On 8/3/2022 6:55 AM, Richard W.M. Jones wrote:
On Sun, Jul 31, 2022 at 03:33:51PM +0200, Kevin Kofler via devel wrote:
Jerry James wrote:
On Sat, Jul 30, 2022 at 10:35 AM Kevin Kofler via devel
<[email protected]> wrote:
What I see is that the hacks that you apply to configure are apparently
not working:
checking command to parse /usr/bin/nm -B output from gcc object...
./configure: line 7304: -e 's/^T .* \(.*\)$/extern int \1();/p' -e
's/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/extern char \1;/p': No such file
or directory
I think that's redhat-rpm-config. See %_fix_broken_configure_for_lto
in /usr/lib/rpm/redhat/macros. I see the same output from every
package I maintain that uses autoconf-generated configure scripts.
So somebody needs to fix redhat-rpm-config then. It's funny when something
called "fix_broken_configure" produces… a broken configure. ;-)
That macro looks very hairy.
They are 100% totally insane. I suspect we've got a quoting issue that
needs to be fixed.
At some point we should just require autoreconf. I think Debian have
been advising (not requiring) that for a while:
https://wiki.debian.org/Autoreconf
That would eliminate the need for those crazy macros. The problem is
many packages have configury bits that are ancient and can't be rebuilt
with modern autotools.
Jeff
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
