Hi all,
What is the status of libtool support for the icc compiler on Linux?
Right now, it causes a problem because the "wl" variable in the generated
libtool file should be set to "-Wl," instead of "", which is what it
currently does. I tried it with libtool 1.4.3 and autoconf 2.56 (2.57
didn't w
Bill,
There is no support for icc in 1.4.3, but there is support in CVS
Libtool.
Robert
Bill Wendling wrote:
>
> Hi all,
>
> What is the status of libtool support for the icc compiler on Linux?
> Right now, it causes a problem because the "wl" variable in the generated
> libtool file should be
For cxx on "osf4* | osf5*", libtool uses
printf "-exported_symbol "
as part of archive_expsym_cmds. Unfortunately bash 2.05b objects to
this with
printf: -e: invalid option
The bash doco doesn't mention any options for printf, but I suppose it
parses them in the usual way. Unl
I wrote:
>
> Using "printf -- -exported_symbol " seems to work with both bash and
> /usr/bin/printf. Unless anyone knows better perhaps this would be a
> good change.
Ah, sorry, I just tried "dash", the Almquist shell on Debian, and its
builtin gives "--" for "printf --". A better way to avoid a
Kevin Ryde wrote:
>
> I wrote:
> >
> > Using "printf -- -exported_symbol " seems to work with both bash and
> > /usr/bin/printf. Unless anyone knows better perhaps this would be a
> > good change.
>
> Ah, sorry, I just tried "dash", the Almquist shell on Debian, and its
> builtin gives "--" for
Bruce Korb <[EMAIL PROTECTED]> writes:
>
> Any particular problem with:
>
> echo '-exported_symbol '
Offhand I can't give an example problem, but autoconf "Limitations of
Builtins" specifically advises against trying to echo anything
starting with "-".
_
Hi,
When trying to build some apps, I got this :
[...]
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
*** Warning: the command libtool uses to detect shared libraries,
*** /usr/bin/file, produces output that libtool cannot recognize.
*
