unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: hanwen@cs.uu.nl, guile-devel@gnu.org, mvo@zagadka.de
Subject: Re: Cygwin patch for 1.6.4
Date: Thu, 02 Oct 2003 19:34:37 +0200	[thread overview]
Message-ID: <87smmbmtle.fsf@peder.flower> (raw)
In-Reply-To: <87wubnmtqn.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Thu, 02 Oct 2003 19:31:28 +0200")

[-- Attachment #1: Type: text/plain, Size: 278 bytes --]

Jan Nieuwenhuizen writes:

> With the next version of libtool, I merely updated ltdl.c and ltdl.h
> from libtool CVS, as were in the previous patch I sent.  Attached
> seperately now.

Really.  So, I'm not sure what guile needs (on other platforms?)
besides these diffs.

Jan.


[-- Attachment #2: ltdl.h.diff --]
[-- Type: text/plain, Size: 741 bytes --]

--- /netrel/src/guile-1.6.4-14/libguile-ltdl/upstream/ltdl.h	2003-10-01 19:49:03.000000000 +0200
+++ raw-ltdl.guilemod.h	2003-10-01 20:59:24.000000000 +0200
@@ -28,6 +28,7 @@
 #ifndef LTDL_H
 #define LTDL_H 1
 
+#include "guile-ltdl.h"
 #include <sys/types.h>		/* for size_t declaration */
 
 \f
@@ -206,9 +207,11 @@
    libltdl relies on a featureful realloc, but if you are sure yours
    has the right semantics then you can assign it directly.  Generally,
    it is safe to assign just a malloc() and a free() function.  */
+#if 0
 LT_SCOPE  lt_ptr   (*lt_dlmalloc)	LT_PARAMS((size_t size));
 LT_SCOPE  lt_ptr   (*lt_dlrealloc)	LT_PARAMS((lt_ptr ptr, size_t size));
 LT_SCOPE  void	   (*lt_dlfree)		LT_PARAMS((lt_ptr ptr));
+#endif
 
 
 

[-- Attachment #3: ltdl.c.diff --]
[-- Type: text/plain, Size: 425 bytes --]

--- /netrel/src/guile-1.6.4-14/libguile-ltdl/upstream/ltdl.c	2003-10-01 19:48:56.000000000 +0200
+++ raw-ltdl.guilemod.c	2003-10-01 20:31:34.000000000 +0200
@@ -26,7 +26,7 @@
 */
 
 #if HAVE_CONFIG_H
-#  include <config.h>
+#  include "config.h"
 #endif
 
 #if HAVE_UNISTD_H
@@ -124,7 +124,7 @@
 #  define assert(arg)	((void) 0)
 #endif
 
-#include "ltdl.h"
+#include "raw-ltdl.h"
 
 #if WITH_DMALLOC
 #  include <dmalloc.h>

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]



-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

[-- Attachment #5: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

  reply	other threads:[~2003-10-02 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16225.62509.832674.84224@localhost.localdomain>
2003-10-01 19:57 ` Cygwin patch for 1.6.4 [WAS: When is 1.8 going to be released] Jan Nieuwenhuizen
2003-10-01 22:28   ` Cygwin patch for 1.6.4 Rob Browning
2003-10-02  7:21     ` Jan Nieuwenhuizen
2003-10-02 16:18       ` Rob Browning
2003-10-02 17:31         ` Jan Nieuwenhuizen
2003-10-02 17:34           ` Jan Nieuwenhuizen [this message]
2003-10-12 18:50           ` Rob Browning
2003-10-02  1:33   ` Kevin Ryde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87smmbmtle.fsf@peder.flower \
    --to=janneke@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=hanwen@cs.uu.nl \
    --cc=mvo@zagadka.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).