public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Robby Griffin <rmg@yakshavers.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: libtool@gnu.org, Daniel Corbe <daniel.junkmail@gmail.com>,
		binutils@sourceware.org
Subject: Re: unrecognized option `-dynamic'
Date: Sat, 17 Jun 2006 08:38:00 -0000	[thread overview]
Message-ID: <bd937fc2c289cdf8be47196cbe869c12@yakshavers.com> (raw)
In-Reply-To: <20060616204220.GH7196@iam.uni-bonn.de>

On Jun 16, 2006, at 15:42, Ralf Wildenhues wrote:

>> I'm attempting to rebuild libtool and binutils on Mac OS X 10.4.6 and
>> I'm running into the following issue:
>
>> /bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2 -no-undefined  -o
>> libltdl/dlopen.la  -module -avoid-version libltdl/loaders/dlopen.lo
>> -ldl
>> libtool: link: rm -fr  libltdl/.libs/dlopen.a
>> libtool: link: ar cru libltdl/.libs/dlopen.a 
>> libltdl/loaders/.libs/dlopen.o
>> ranlib: unrecognized option `-q'
>> Try `ranlib --help' for more information.
>> ar: internal ranlib command failed
>
> This looks like a bug in 'ar' to me.

I think it's yet another instance of the confusion between GNU libtool 
and MacOS X's included libtool, which is a completely different 
program. On a MacOS X system, /usr/bin/ranlib is a symlink to 
/usr/bin/libtool, which has the following usage:

        libtool  -static  -o  output  [ -sacLT ] [ - ] [ -arch_only 
arch_type ]
        file...  [-filelist listfile[,dirname]]

        libtool -dynamic -o output [ -install_name name ] [ 
-compatibility_ver-
        sion  number ] [ -current_version number ] [ link editor flags ] 
[ -v ]
        [ -noall_load ] [ - ] [  -arch_only  arch_type  ]  file...   
[-filelist
        listfile[,dirname]]

        ranlib [ -sactfLT ] [ - ] archive...

Chances are Daniel's overwritten the Apple libtool (and thus ranlib) 
with GNU libtool. OS X users should take pains to avoid installing GNU 
libtool into /usr/bin/, and maybe GNU libtool ought to make it more 
difficult for them to do so...

	--Robby

      parent reply	other threads:[~2006-06-16 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 20:42 Daniel Corbe
2006-06-16 20:59 ` Ralf Wildenhues
2006-06-16 21:05   ` Daniel Corbe
2006-06-16 21:11   ` Daniel Corbe
2006-06-16 21:19     ` Daniel Corbe
2006-06-17  8:38   ` Robby Griffin [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd937fc2c289cdf8be47196cbe869c12@yakshavers.com \
    --to=rmg@yakshavers.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=daniel.junkmail@gmail.com \
    --cc=libtool@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).