From: "H . J . Lu" <hjl@lucon.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
Adrian.Hulse@taec.toshiba.com, linux-mips@oss.sgi.com
Subject: Re: libtool warning on redhat 7.1 native mipsel compile
Date: Mon, 14 Jan 2002 09:56:05 -0800 [thread overview]
Message-ID: <20020114095605.D30946@lucon.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1020114123330.10091B-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Jan 14, 2002 at 12:35:57PM +0100
On Mon, Jan 14, 2002 at 12:35:57PM +0100, Maciej W. Rozycki wrote:
> On Fri, 11 Jan 2002, H . J . Lu wrote:
>
> > ELF [0-9][0-9]*-bit [LM]SB [.]* (shared object | dynamic lib)
>
> Why not simply "lt_cv_deplibs_check_method=pass_all" like for other sane
> Linux platforms? I'm running libtool in such a configuration since May
> with no negative side effects.
>
Please follow
http://sources.redhat.com/ml/binutils/2001-10/msg00358.html
http://sources.redhat.com/ml/binutils/2001-10/msg00406.html
H.J.
next prev parent reply other threads:[~2002-01-14 18:56 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
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 [this message]
-- 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=20020114095605.D30946@lucon.org \
--to=hjl@lucon.org \
--cc=Adrian.Hulse@taec.toshiba.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@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