From: Bruce Korb <bkorb@gnu.org>
Cc: Harlan Stenn <stenn@ntp.isc.org>, guile-devel@gnu.org, reg@deneb.dwf.com
Subject: Re: [ntp:hackers/Guile devel] ntp-dev changes
Date: Sun, 16 Apr 2006 09:08:47 -0700 [thread overview]
Message-ID: <44426C0F.8000600@gnu.org> (raw)
In-Reply-To: <200604152237.k3FMbWoQ024530@deneb.dwf.com>
Reg Clemens wrote:
> Humm.
> Linux Fedora4 came with gcc 4.00 and was upgraded to 4.0.2 as some point,
> so I dont easily have access to an older version on my home machines.
> Checking at the Lab, where I still have Fedora2 loaded, I find gcc 3.3.3,
> and guile-1.6.7 DOES compile there.
>
> Still, the error reported sounds more like something has changed between
> OS levels than a problem with the compiler itself. I can try moving the
> compiled version back home, but from what Harlan says, I wont be able
> to test it for a week or so.
Chasing through Guile sources, I get this:
> #ifdef DYNAMIC_LINKING
> /* libtool automagically inserts this variable into your executable... */
> extern const scm_lt_dlsymlist lt_preloaded_symbols[]; // Line 91
> scm_lt_dlpreload_default (lt_preloaded_symbols);
> #endif
The message is:
> guile.c: In function 'main':
> guile.c:91: error: array type has incomplete element type
> guile.c:91: warning: unused variable 'lt_preloaded_symbols'
So, it seems to me that there is an inconsistency in the build environment
and the defining of DYNAMIC_LINKING. The problem is almost certainly
in Guile. But, I have heard complaints (that I only fuzzily remember)
that Guile does not build with GCC-4. Assuming I am remembering
correctly :) , the headers that GCC-4 bring along with itself are
causing "scm_lt_dlsymlist" to be an incomplete type and "scm_lt_dlpreload_default"
to be a macro that expands to the empty string (unreferenced variable).
I'll poke into this a bit more, but I do wish a Guile developer could
chime in with a word or two.
Thanks - Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-04-16 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060413200537.1D78D39B52@ntp1.ntp.isc.org>
2006-04-15 15:39 ` [ntp:hackers/Guile devel] ntp-dev changes Bruce Korb
2006-04-15 17:25 ` Reg Clemens
2006-04-15 17:40 ` Bruce Korb
2006-04-15 22:37 ` Reg Clemens
2006-04-16 16:08 ` Bruce Korb [this message]
2006-04-16 16:36 ` Bruce Korb
2006-04-16 16:50 ` Rob Browning
2006-04-16 16:55 ` Bruce Korb
2006-04-17 1:02 ` Kevin Ryde
2006-04-16 22:34 ` 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=44426C0F.8000600@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@gnu.org \
--cc=reg@deneb.dwf.com \
--cc=stenn@ntp.isc.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).