From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: Guile 1.9.14 & GIT version linking errror
Date: Wed, 26 Jan 2011 20:30:07 +0100 [thread overview]
Message-ID: <m3lj27ea4g.fsf@unquote.localdomain> (raw)
In-Reply-To: <87k4i3go1o.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 17 Jan 2011 23:31:31 +0100")
On Mon 17 Jan 2011 23:31, ludo@gnu.org (Ludovic Courtès) writes:
> Hans Aberg <haberg-1@telia.com> writes:
>
>> I have GCC 4.0.1.
>
> No you don’t. This is Apple’s compiler, based on GCC, but with its own
> inline semantics, and a behavior different from that of GCC.
>
> Anyway you found a workaround, which is what matters. :-)
When I compile on a Mac 10.5 system, I have to export CC=gcc-4.2. Both
the Apple 4.0.1 and whatever their 4.2 compiler are installed, but `gcc'
is the old one.
How these compilers do inlining is one of the salient differences
between the two. I made sure to compile a new gmp, using gcc-4.2, and
compile Guile with that compiler as well.
Happy hacking,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-01-26 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13B7D376-7BFD-4236-B6EF-5BF70FE248B7@telia.com>
[not found] ` <87lj2lgavf.fsf@ossau.uklinux.net>
2011-01-15 23:11 ` Macro expansion Hans Aberg
2011-01-16 10:00 ` Guile 1.9.14 & GIT version linking errror Hans Aberg
2011-01-16 10:18 ` Neil Jerram
2011-01-16 10:27 ` Neil Jerram
2011-01-16 10:38 ` Hans Aberg
2011-01-16 12:04 ` Hans Aberg
2011-01-16 14:32 ` Hans Aberg
2011-01-17 22:31 ` Ludovic Courtès
2011-01-26 19:30 ` Andy Wingo [this message]
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=m3lj27ea4g.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=ludo@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).