[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Bug#207475: libtool: wrongly hides important compiler output]

From: Scott James Remnant
Subject: [Fwd: Bug#207475: libtool: wrongly hides important compiler output]
Date: Wed, 01 Oct 2003 01:26:18 +0100

Forwarded for discussion purposes ...

I can see Sam's point, but I can also see the reason for suppressing one
of two near-identical compilations.


-----Forwarded Message-----
From: Sam Hocevar <address@hidden>
To: Debian Bug Tracking System <address@hidden>
Subject: Bug#207475: libtool: wrongly hides important compiler output
Date: Wed, 27 Aug 2003 12:40:32 +0200

Package: libtool
Version: 1.5-1 (not installed)
Severity: normal

   My generated libtool scripts contain the following lines (coming from
/usr/share/libtool/, line 725):

      # Allow error messages only from the first compilation.
      suppress_output=' >/dev/null 2>&1'

   Which means that if the -fPIC compilation succeeded, it sends the
output of the non-PIC compilation to /dev/null, wrongly assuming that
if a file builds in PIC mode it will build in non-PIC mode (which is
obviously wrong since one can put broken code between #ifndef PIC). It
is then highly irritating to get a build error from the buildd that
simply says "Error 1".

   I suggest that this suppress_output line either be simply removed,
because it is simply wrong to hide meaningful output from the user, or
at least be made configurable.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux c18 2.4.21-rc5 #2 Wed May 28 22:10:14 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=fr_FR

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]