Alexandre Oliva wrote:
> On May 29, 2000, Stephan Kulow <[EMAIL PROTECTED]> wrote:
>
> > This is a bug in gcc at least til 2.8.1 (no 2.95 here at the
> > moment):
>
> > _IO_do_write0x8c
> > /opt/GCC281/lib/libstdc++.
> > a(stdiostream.o)
>
> Not a bug. It's just that libs
On Solaris, libtool does not allow me to do the following:
> /bin/sh ../libtool --mode=link gcc -g -O2 -o libfoo.la -rpath
/usr/local/lib foo.lo /usr/local/lib/libbar.a
libtool: link: cannot build libtool library `libfoo.la' from non-libtool
objects: /usr/local/lib/libbar.a
and yet the Solari
Thomas Tanner wrote:
> Yep. That's already implemented in CVS libtool:
Just a minor question ... does CVS libtool require CVS autoconf and/or CVS
automake?
--
Thanks,
Paul
Alexandre Oliva wrote:
> On Jul 26, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> > Why is it a warning? This should be an error. If I tell it
> > "use -lgdi32" it should use it or error out.
>
> Nope. -lgdi32 is being recorded as a required dependency, and it will
> be linked in when any executa
Alexandre Oliva wrote:
> On Aug 10, 2000, Paul Berrevoets <[EMAIL PROTECTED]> wrote:
>
> > Alexandre Oliva wrote:
> >> On Jul 26, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> >> > Why is it a warning? This should be an error. If I tell it
>
The ChangeLog contains the following entry:
1999-04-25 Alexandre Oliva <[EMAIL PROTECTED]>
...
* ltconfig.in (hpux*, hardcode_minus_L): Set to yes.
(hpux*, hardcode_libdir_flag_spec): Do not use +s by default.
(hpux*, shlibpath_overrides_runpath): Set to no.
foo
foo_LDFLAGS = -L$(libdir) -lbar
--
Regards,
Paul
Alexandre Oliva wrote:
> On Oct 26, 2000, Paul Berrevoets <[EMAIL PROTECTED]> wrote:
>
> > (hpux*, hardcode_libdir_flag_spec): Do not use +s by default.
>
> > What was the rational for this?
>
> It
settings the way I need it,
but libtool.m4 won't allow such a configuration. Are these settings
inconsistent with each other?
hardcode_action=relink
hardcode_direct=no
hardcode_minus_L=yes
--
Thanks,
Paul
Paul Berrevoets wrote:
> I've tried this now, but unfortunately
, but we have since
installed a patch which causes expr to return '' on subexpression match
failure.
--
Regards,
Paul
2000-11-16 Paul Berrevoets <[EMAIL PROTECTED]>
* ltmain.in: Check for '' and '0' when using expr subexpressions.
--- ltmai
re being expanded by m4
into '0', '' and '' respectively. '[$]#', '[$]2' and '[$]3' should be
used instead. The patch is attached.
--
Regards,
Paul Berrevoets
2000-11-18 Paul Berrevoets <[EMAIL PROTECTED]>
* libtool
10 matches
Mail list logo