From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: GUILE 1.6 CVS doesn't compile
Date: Mon, 11 Jul 2005 10:10:43 +1000 [thread overview]
Message-ID: <8764vinqws.fsf@zip.com.au> (raw)
In-Reply-To: 42D10CF5.7070405@xs4all.nl
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> make check
>
> isn't complaining.
I think it works only because that preload array is empty. There's a
terminating zero entry, so the fetch from there gives NULL, and
lt_dlpreload_default can tolerate NULL (it looks like NULL is what's
there if you never call lt_dlpreload_default at all).
If the array wasn't empty the fetch would be the address of the first
symbol name string, and interpreting that as structs would bomb.
I suppose the fix is to define the struct, perhaps per below. Or
perhaps the lt_dlpreload_default call isn't needed at all if there's
no -dlopen or -dlpreopen in the link.
[-- Attachment #2: libguile-ltdl.diff --]
[-- Type: text/plain, Size: 1443 bytes --]
Index: guile-ltdl.h
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/libguile-ltdl/guile-ltdl.h,v
retrieving revision 1.2.2.2
diff -u -r1.2.2.2 guile-ltdl.h
--- guile-ltdl.h 23 May 2005 20:15:31 -0000 1.2.2.2
+++ guile-ltdl.h 10 Jul 2005 23:58:57 -0000
@@ -27,8 +27,11 @@
#define SCM_LTDL_H 1
typedef struct scm_i_lt_dlhandle_struct *scm_lt_dlhandle;
-typedef struct scm_i_lt_dlsymlist_struct scm_lt_dlsymlist;
typedef void * scm_lt_ptr;
+typedef struct scm_i_lt_dlsymlist_struct {
+ const char *name;
+ scm_lt_ptr address;
+} scm_lt_dlsymlist;
void scm_lt_dlpreload_default (const scm_lt_dlsymlist *preloads);
int scm_lt_dlinit (void);
Index: raw-ltdl.h
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/libguile-ltdl/raw-ltdl.h,v
retrieving revision 1.2.2.2
diff -u -r1.2.2.2 raw-ltdl.h
--- raw-ltdl.h 23 May 2005 20:15:31 -0000 1.2.2.2
+++ raw-ltdl.h 10 Jul 2005 23:58:57 -0000
@@ -211,10 +211,7 @@
/* A preopened symbol. Arrays of this type comprise the exported
symbols for a dlpreopened module. */
-typedef struct SCM_INSERTED_DLSYMLIST_STRUCT_DECL {
- const char *name;
- lt_ptr address;
-} lt_dlsymlist;
+typedef struct scm_i_lt_dlsymlist_struct lt_dlsymlist;
SCMLTXT int lt_dlpreload LT_PARAMS((const lt_dlsymlist *preloaded));
SCMLTXT int lt_dlpreload_default
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-07-11 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 12:33 GUILE 1.6 CVS doesn't compile Han-Wen Nienhuys
2005-06-10 12:34 ` Han-Wen Nienhuys
2005-06-10 21:34 ` Kevin Ryde
2005-06-14 1:01 ` Han-Wen Nienhuys
2005-06-19 13:21 ` Han-Wen Nienhuys
2005-07-10 1:47 ` Kevin Ryde
2005-07-10 11:56 ` Han-Wen Nienhuys
2005-07-11 0:10 ` Kevin Ryde [this message]
2005-07-11 10:39 ` Han-Wen Nienhuys
2005-07-11 23:41 ` Kevin Ryde
2005-07-11 10:51 ` Han-Wen Nienhuys
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=8764vinqws.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
/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).