GNU logs - #20947, boring messages

Message sent to bug-libtool@HIDDEN:

Subject: bug#20947: libtool 2.4.2 is not robust to a missing global_symbol_pipe
Resent-From: Philip Chimento <philip.chimento@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Tue, 30 Jun 2015 23:11:03 +0000
Resent-Message-ID: <handler.20947.B.14357058421714 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 20947 <at> debbugs.gnu.org
MIME-Version: 1.0
Date: Tue, 30 Jun 2015 15:24:41 -0700
Message-ID: <CAHbXgc0K023dW3b1aLN4L4-GcHVOcqig8=AoQdmU7FumBV3i9A@HIDDEN>
From: Philip Chimento <philip.chimento@HIDDEN>
Content-Type: multipart/alternative; boundary=001a1136cbd828dcdd0519c3ac66
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--001a1136cbd828dcdd0519c3ac66
Content-Type: text/plain; charset=UTF-8

This is a difficult-to-reproduce bug since it only occurs due to outside
influences. However, I believe libtool's behaviour could be improved to
make it more obvious what is going on when the bug occurs.

Many instances of the symptom can be found by doing an internet search for
"libtool global_symbol_pipe". Basically the configure check for the sed
expression to parse the output of nm can fail, without causing configure to
abort.

    checking command to parse /usr/bin/nm -B output from gcc object...
failed

This results in the variable global_symbol_pipe being empty in the
generated libtool script, which causes compilation to fail later on:

    libtool: link: /usr/bin/nm -B <OBJECT-FILES> | | /bin/sed 's/.* //' |
sort | uniq > <EXPORTED-SYMBOL-FILE>

    ./libtool: eval: line <LINE>: syntax error near unexpected token `|'

(The empty space between the pipes is where the empty global_symbol_pipe
variable is plugged in.)

That this happens is not libtool's fault, it's generally caused by a
misconfigured nm. However, I believe it would lead to fewer headaches for
libtool users if configure aborted with an explanation, or the libtool
script itself was more robust to the empty variable and didn't try to pipe
nm output through nothing.

Regards,
-- 
Philip

--001a1136cbd828dcdd0519c3ac66
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is a difficult-to-reproduce bug since it only occurs =
due to outside influences. However, I believe libtool&#39;s behaviour could=
 be improved to make it more obvious what is going on when the bug occurs.<=
div><br></div><div>Many instances of the symptom can be found by doing an i=
nternet search for &quot;libtool global_symbol_pipe&quot;. Basically the co=
nfigure check for the sed expression to parse the output of nm can fail, wi=
thout causing configure to abort.</div><div><br></div><div>=C2=A0 =C2=A0=C2=
=A0checking command to parse /usr/bin/nm -B output from gcc object... faile=
d</div><div><br></div><div>This results in the variable global_symbol_pipe =
being empty in the generated libtool script, which causes compilation to fa=
il later on:</div><br>=C2=A0 =C2=A0 libtool: link: /usr/bin/nm -B &lt;OBJEC=
T-FILES&gt; | | /bin/sed &#39;s/.* //&#39; | sort | uniq &gt; &lt;EXPORTED-=
SYMBOL-FILE&gt;<br><br>=C2=A0 =C2=A0 ./libtool: eval: line &lt;LINE&gt;: sy=
ntax error near unexpected token `|&#39;<div><br></div><div>(The empty spac=
e between the pipes is where the empty global_symbol_pipe variable is plugg=
ed in.)</div><div><br></div><div>That this happens is not libtool&#39;s fau=
lt, it&#39;s generally caused by a misconfigured nm. However, I believe it =
would lead to fewer headaches for libtool users if configure aborted with a=
n explanation, or the libtool script itself was more robust to the empty va=
riable and didn&#39;t try to pipe nm output through nothing.<br><div><br><d=
iv>Regards,</div>-- <br><div class=3D"gmail_signature">Philip</div>
</div></div></div>

--001a1136cbd828dcdd0519c3ac66--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Philip Chimento <philip.chimento@HIDDEN>
Subject: bug#20947: Acknowledgement (libtool 2.4.2 is not robust to a
 missing global_symbol_pipe)
Message-ID: <handler.20947.B.14357058421714.ack <at> debbugs.gnu.org>
References: <CAHbXgc0K023dW3b1aLN4L4-GcHVOcqig8=AoQdmU7FumBV3i9A@HIDDEN>
X-Gnu-PR-Message: ack 20947
X-Gnu-PR-Package: libtool
Reply-To: 20947 <at> debbugs.gnu.org
Date: Tue, 30 Jun 2015 23:11:04 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-libtool@HIDDEN

If you wish to submit further information on this problem, please
send it to 20947 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
20947: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D20947
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.