From: Ralf Baechle <ralf@oss.sgi.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Adrian.Hulse@taec.toshiba.com, linux-mips@oss.sgi.com
Subject: Re: libtool warning on redhat 7.1 native mipsel compile
Date: Fri, 11 Jan 2002 21:26:20 -0800 [thread overview]
Message-ID: <20020111212620.A4809@dea.linux-mips.net> (raw)
In-Reply-To: <20020111120806.A28902@lucon.org>; from hjl@lucon.org on Fri, Jan 11, 2002 at 12:08:06PM -0800
On Fri, Jan 11, 2002 at 12:08:06PM -0800, H . J . Lu wrote:
> > I don't know for sure just yet, the package takes a long time to compile.
> > The last time I compiled the package it failed to build - whether it is due
> > to the warnings or not I don't really know - maybe not.
> >
>
> libtool is very fragile. If it doesn't cause the failure, I won't touch
> it.
This bug may result in libraries not getting linked against certain other
libraries thus DT_NEEDED entries missing. Frequently that's harmless but
it breaks a few packages. I remember fixing this in a large number of
RH 7.0 packages.
Bug are rarely harmless just their consequences are subtle.
Ralf
next prev parent reply other threads:[~2002-01-12 6:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 20:08 libtool warning on redhat 7.1 native mipsel compile Adrian.Hulse
2002-01-11 20:08 ` H . J . Lu
2002-01-12 5:26 ` Ralf Baechle [this message]
2002-01-12 5:42 ` H . J . Lu
2002-01-12 5:48 ` Ralf Baechle
2002-01-12 13:36 ` Robin Humble
2002-01-12 17:22 ` H . J . Lu
2002-01-13 4:04 ` Robin Humble
2002-01-13 6:27 ` H . J . Lu
2002-01-14 11:44 ` Maciej W. Rozycki
2002-01-14 17:50 ` H . J . Lu
2002-01-15 12:57 ` Brian Murphy
2002-01-15 15:46 ` H . J . Lu
2002-01-14 11:35 ` Maciej W. Rozycki
2002-01-14 17:56 ` H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 19:53 Adrian.Hulse
2002-01-11 19:56 ` H . J . Lu
2002-01-11 20:12 ` Maciej W. Rozycki
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=20020111212620.A4809@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=Adrian.Hulse@taec.toshiba.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
/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