This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libtool sending output to /dev/null [Was: Re: GCC build failedfor native with your patch on 2002-06-02T22:30:03Z.]
- From: Andreas Schwab <schwab at suse dot de>
- To: Marc Espie <espie at quatramaran dot ens dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 05 Jun 2002 13:56:13 +0200
- Subject: Re: libtool sending output to /dev/null [Was: Re: GCC build failedfor native with your patch on 2002-06-02T22:30:03Z.]
- References: <200206030144.g531iqx13347@maat.sfbay.redhat.com><20020603095755.GF27711@atrey.karlin.mff.cuni.cz><20020603061242.A9370@disaster.basement.lan><20020603101458.GG27711@atrey.karlin.mff.cuni.cz><20020603122106.GA2041@daikokuya.demon.co.uk><20020603090021.A10452@disaster.basement.lan> <jmsn44uyyd.fsf -@desire.geoffk.org> <200206041015.g54AFGu28430@quatramaran.ens.fr>
Marc Espie <espie@quatramaran.ens.fr> writes:
|> I'd much rather see the actual output of the commands libtool is running.
|> Some commands do issue useful diagnostics, which are not failures per-se,
|> but lead to tracking bugs in an easy way later.
|>
|> In fact, OpenBSD ld warns about RSS relocations, which are coming to non-pic
|> code being linked as pic code (which leads to inefficient shared libraries).
|>
|> If you redirect the warnings, you will never know things are wrong. You
|> will just notice that your shared libraries consume a fairly large amount
|> of memory.
The redirection only happens during compilation, not during linking, so
this case is not affected.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."