public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Corbe" <daniel.junkmail@gmail.com>
To: "Daniel Corbe" <daniel.junkmail@gmail.com>,
	binutils@sourceware.org,  	libtool@gnu.org
Subject: Re: unrecognized option `-dynamic'
Date: Fri, 16 Jun 2006 21:11:00 -0000	[thread overview]
Message-ID: <cceb89df0606161405w65ebffcbu218b559303332fcd@mail.gmail.com> (raw)
In-Reply-To: <20060616204220.GH7196@iam.uni-bonn.de>

Even when building libtool I see the -dynamic switch:

jomama:/usr/local/src/libtool-1.5.22 root# make
Making all in .
make[1]: Nothing to be done for `all-am'.
Making all in libltdl
make  all-am
/bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -no-undefined
-version-info 4:4:1  -o libltdl.la -rpath /usr/local/lib ltdl.lo -ldl
gcc -dynamiclib  -o .libs/libltdl.3.1.4.dylib  .libs/ltdl.o  -ldl
-install_name  /usr/local/lib/libltdl.3.dylib
-Wl,-compatibility_version -Wl,5 -Wl,-current_version -Wl,5.4
libtool: unrecognized option `-dynamic'
Try `libtool --help' for more information.

On 6/16/06, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> Hello Daniel,
>
> * Daniel Corbe wrote on Fri, Jun 16, 2006 at 10:32:36PM CEST:
> >
> > I apologize for cross-posting but I don't know where I should be
> > loking to resolve this issue.
>
> I think you may be running into more than one issue here.
>
> > 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.
>
> > (binutils):
> > /bin/sh .././libiberty/../mkinstalldirs /usr/lib
> > /usr/local/bin/install -c -m 644 ./libiberty.a /usr/lib/./libiberty.an
> > ( cd /usr/lib ; ranlib ./libiberty.an )
> > *** Warning: inferring the mode of operation is deprecated.
> > *** Future versions of Libtool will require --mode=MODE be specified.
> > ranlib: warning: cannot infer operation mode from `./libiberty.an'
> > ranlib: you must specify a MODE
> > Try `ranlib --help' for more information.
>
> This, however, looks really weird, for more than one reason:
> The prefix should be 'libtool', not 'ranlib'.  The extra 'n' at the end
> of the archive name looks like the computation for the echo command and
> its use did not match.  Did you make sure both the Libtool macros and
> the ltmain.sh file are from the same Libtool version?
>
> Hmm.  The last time I looked at binutils, which was quite a while ago,
> it wasn't ready for a recent Libtool version, but using and shipping
> with the ltmain.sh and the macros of 1.4.x.  If that hasn't changed,
> then some work is needed there.
>
> > ranlib --dynamic and libtool --dynamic causes some of my other
> > software builds to fail.
>
> Hmm, where in the two above messages does '--dynamic' come into play?
>
> > Is there a process I should be following to build both of these apps
> > correctly?
>
> Well, as long as binutils needs ancient Libtool-1.4.x, it seems it would
> need this changed first.
>
> > libtool is from CVS today and binutils is 2.16
>
> But you are well aware that a CVS version isn't for the faint of heart?
> The latest stable release of Libtool is 1.5.22.
>
> Cheers,
> Ralf
>

  parent reply	other threads:[~2006-06-16 21:05 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 [this message]
2006-06-16 21:19     ` Daniel Corbe
2006-06-17  8:38   ` Robby Griffin

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=cceb89df0606161405w65ebffcbu218b559303332fcd@mail.gmail.com \
    --to=daniel.junkmail@gmail.com \
    --cc=binutils@sourceware.org \
    --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).