From: Jay Cotton <jay@fleeingrabbit.com>
Subject: Re: build error on my system (Mac OS 10.4.5)
Date: Wed, 29 Mar 2006 19:11:22 -0500 [thread overview]
Message-ID: <CABE2628-9FE9-4460-8075-6A20BFF5DCC4@fleeingrabbit.com> (raw)
In-Reply-To: <87slp1q6t1.fsf@zip.com.au>
On Mar 29, 2006, at 4:28 PM, Kevin Ryde wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>>
>> The configure script tests for socklen_t in
>> the wrong way. It must do something like I posted some weeks ago.
>
> Oops, that must have gone through to the keeper.
> The configure change below might do the right thing.
>
> <configure.in.socklen_t.diff>
Thanks for the help, everybody. I made the changes to configure.in
suggested here:
http://lists.gnu.org/archive/html/guile-devel/2006-02/msg00039.html
and re-ran autoconf. Seems to have worked, because I was able to
continue to the next error. :-/
This time the problem seems to be with either GNU MP or libtool. I
installed the latest versions of libtool and GNU MP, and ran make
check on both of them, before I set out to build guile. (I'm not sure
how to verify this, however, as a sanity check.)
Here's the error:
gcc -dynamiclib -o .libs/libguile.17.0.0.dylib [... i cut out the
rest of this huge build line ... ]
ld: common symbols not allowed with MH_DYLIB output format with the -
multi_module option
/usr/local/lib/libgmp.a(mp_bpl.o) definition of common ___gmp_junk
(size 4)
/usr/bin/libtool: internal link edit command failed
make[2]: *** [libguile.la] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Regards,
Jay
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-30 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 21:55 build error on my system (Mac OS 10.4.5) Jay Cotton
2006-03-29 0:34 ` Kevin Ryde
2006-03-29 7:23 ` Michael Tuexen
[not found] ` <FBE8E503-00A6-4CFE-AB12-8A7FEA0B1657@fleeingrabbit.com>
2006-03-29 14:35 ` Michael Tuexen
2006-03-29 21:28 ` Kevin Ryde
2006-03-30 0:11 ` Jay Cotton [this message]
2006-03-29 15:01 ` Jay Cotton
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=CABE2628-9FE9-4460-8075-6A20BFF5DCC4@fleeingrabbit.com \
--to=jay@fleeingrabbit.com \
/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).