* Re: unrecognized option `-dynamic'
2006-06-16 20:59 ` Ralf Wildenhues
@ 2006-06-16 21:05 ` Daniel Corbe
2006-06-16 21:11 ` Daniel Corbe
2006-06-17 8:38 ` Robby Griffin
2 siblings, 0 replies; 6+ messages in thread
From: Daniel Corbe @ 2006-06-16 21:05 UTC (permalink / raw)
To: Daniel Corbe, binutils, libtool
Well I've attempted to build libtool from the 1.5.22 sources as well
and I run into the same issue. That's why I originally attempted CVS.
I fear that I've left my build enviornment in too inconsistent of a
state to be repaird..
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
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: unrecognized option `-dynamic'
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
2 siblings, 1 reply; 6+ messages in thread
From: Daniel Corbe @ 2006-06-16 21:11 UTC (permalink / raw)
To: Daniel Corbe, binutils, libtool
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
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: unrecognized option `-dynamic'
2006-06-16 21:11 ` Daniel Corbe
@ 2006-06-16 21:19 ` Daniel Corbe
0 siblings, 0 replies; 6+ messages in thread
From: Daniel Corbe @ 2006-06-16 21:19 UTC (permalink / raw)
To: Daniel Corbe, binutils, libtool
Never mind, apparantly apple uses their own libtool
Sorry guys!
-Daniel
On 6/16/06, Daniel Corbe <daniel.junkmail@gmail.com> wrote:
> 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
> >
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: unrecognized option `-dynamic'
2006-06-16 20:59 ` Ralf Wildenhues
2006-06-16 21:05 ` Daniel Corbe
2006-06-16 21:11 ` Daniel Corbe
@ 2006-06-17 8:38 ` Robby Griffin
2 siblings, 0 replies; 6+ messages in thread
From: Robby Griffin @ 2006-06-17 8:38 UTC (permalink / raw)
To: Ralf Wildenhues; +Cc: libtool, Daniel Corbe, binutils
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
^ permalink raw reply [flat|nested] 6+ messages in thread