GNU bug report logs -
#40459
Non-reproducible behaviour in libtool < 2.2.7b bootstrapped ltmain.sh
Previous Next
To reply to this bug, email your comments to 40459 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#40459
; Package
guix
.
(Sun, 05 Apr 2020 21:32:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Carl Dong <contact <at> carldong.me>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 05 Apr 2020 21:32:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi Guix!
While investigating a libstdc++.a reproducibility issue, I found that libtool prior to 74c8993c (first included in version 2.2.7b, link: https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=74c8993c178a1386ea5e2363a01d919738402f30) did not sort find output. It seems that many packages (including all released gcc versions so far) are bootstrapped with a libtool < 2.2.7b.
There are probably many ways to approach this, and I propose that we could simply use a somewhat strict regex find and replace on ltmain.sh.
Would love feedback and better ideas!
Cheers,
Carl Dong
Information forwarded
to
bug-guix <at> gnu.org
:
bug#40459
; Package
guix
.
(Mon, 06 Apr 2020 09:22:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 40459 <at> debbugs.gnu.org (full text, mbox):
Hello!
Carl Dong <contact <at> carldong.me> skribis:
> While investigating a libstdc++.a reproducibility issue, I found that
> libtool prior to 74c8993c (first included in version 2.2.7b, link:
> https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=74c8993c178a1386ea5e2363a01d919738402f30)
> did not sort find output.
Right, good ol’days!
> It seems that many packages (including all released gcc versions so
> far) are bootstrapped with a libtool < 2.2.7b.
Ouch, I didn’t expect this.
> There are probably many ways to approach this, and I propose that we could simply use a somewhat strict regex find and replace on ltmain.sh.
Yes, we could add a standard build phase to do that. We just need to
make sure we get the regexp right so it doesn’t break newer ‘ltmain.sh’
scripts.
WDYT?
Ludo’.
This bug report was last modified 5 years and 68 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.