unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: "Frank J. R. Hanstick" <trog24@comcast.net>
Cc: Guile-user@gnu.org
Subject: Re: multo_module
Date: Mon, 22 Oct 2007 12:04:46 +0200	[thread overview]
Message-ID: <87tzojv51d.fsf@laas.fr> (raw)
In-Reply-To: <90E0EC09-6A30-469F-B0B7-439A476E0647@comcast.net> (Frank J. R. Hanstick's message of "Sat\, 20 Oct 2007 21\:29\:36 -0700")

Hi,

"Frank J. R. Hanstick" <trog24@comcast.net> writes:

> /bin/sh ../libtool --tag=CC --mode=link gcc  -g -O2 -Wall -Wmissing- 
> prototypes -Werror   -o libguile.la -rpath /usr/local/lib -lintl -Wl,- 
> framework -Wl,CoreFoundation -version-info 17:1:0 -no-undefined

[...]

> 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

[...]

> 	I had earlier asked about this in simpler form; but, got no
> reply.   The line generating this error is 214 of libtool.  The
> question is,  am I suppose to be getting here (there are lines with
> -single_module  designated).  If the answer is yes, then how does the
> line need to be  changed so that I do not get this error and if no,
> what needs to be  changed to not get here?

Sorry, I'm not familiar at all with Darwin's linker.  I suppose you'll
have to further dig its documentation.

Nevertheless, I think there were report of successful builds on MacOS X
in the past...

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2007-10-22 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21  4:29 multo_module Frank J. R. Hanstick
2007-10-22 10:04 ` Ludovic Courtès [this message]
2007-10-23  1:48   ` multo_module Frank J. R. Hanstick

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=87tzojv51d.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=Guile-user@gnu.org \
    --cc=trog24@comcast.net \
    /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).