* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
@ 2023-01-05 19:23 ` ian at airs dot com
2023-01-05 19:48 ` dave.anglin at bell dot net
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: ian at airs dot com @ 2023-01-05 19:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian at airs dot com
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
Does HP/UX 11.11 use ELF? If so, I guess we need a configure test to see
whether the linker supports the --build-id option. If it doesn't, I guess we
need to skip the debuginfo tests.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
2023-01-05 19:23 ` [Bug libbacktrace/108297] " ian at airs dot com
@ 2023-01-05 19:48 ` dave.anglin at bell dot net
2023-01-05 20:08 ` ian at airs dot com
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: dave.anglin at bell dot net @ 2023-01-05 19:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
--- Comment #2 from dave.anglin at bell dot net ---
On 2023-01-05 2:23 p.m., ian at airs dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
>
> Ian Lance Taylor <ian at airs dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ian at airs dot com
>
> --- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
> Does HP/UX 11.11 use ELF?
The 64-bit target uses ELF.
> If so, I guess we need a configure test to see
> whether the linker supports the --build-id option. If it doesn't, I guess we
> need to skip the debuginfo tests.
Currently, HP ld is the only working linker and it doesn't support the
--build-id option. GNU
ld has problems with shared library support.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
2023-01-05 19:23 ` [Bug libbacktrace/108297] " ian at airs dot com
2023-01-05 19:48 ` dave.anglin at bell dot net
@ 2023-01-05 20:08 ` ian at airs dot com
2023-01-06 15:26 ` danglin at gcc dot gnu.org
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: ian at airs dot com @ 2023-01-05 20:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
--- Comment #3 from Ian Lance Taylor <ian at airs dot com> ---
Created attachment 54196
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54196&action=edit
Potential patch
Does this patch fix the problem for you? Thanks.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
` (2 preceding siblings ...)
2023-01-05 20:08 ` ian at airs dot com
@ 2023-01-06 15:26 ` danglin at gcc dot gnu.org
2023-01-06 17:42 ` cvs-commit at gcc dot gnu.org
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-01-06 15:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
--- Comment #4 from John David Anglin <danglin at gcc dot gnu.org> ---
It appears the --build-id issue is fixed by the change.
But there's still a lto issue breaking make check:
libtool: link: /home/dave/gnu/gcc/objdir64/./prev-gcc/xgcc
-B/home/dave/gnu/gcc/
objdir64/./prev-gcc/ -B/opt/gnu64/gcc/gcc-13/hppa64-hp-hpux11.11/bin/
-B/opt/gnu
64/gcc/gcc-13/hppa64-hp-hpux11.11/bin/
-B/opt/gnu64/gcc/gcc-13/hppa64-hp-hpux11.
11/lib/ -isystem /opt/gnu64/gcc/gcc-13/hppa64-hp-hpux11.11/include -isystem
/opt
/gnu64/gcc/gcc-13/hppa64-hp-hpux11.11/sys-include -fchecking=1 -funwind-tables
-
frandom-seed=btest_lto -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-pr
ototypes -Wold-style-definition -Wmissing-format-attribute -Wcast-qual -g -O
-fl
to -g -O2 -fchecking=1 -s -o btest_lto btest_lto-btest.o btest_lto-testlib.o
./
.libs/libbacktrace.a
ld: Unsatisfied hidden symbol "btest.c.cfb1d6bc". Symbol was referenced from
fil
e /var/tmp//ccuhlRBW.debug.temp.o
ld: Unsatisfied hidden symbol "btest.c.cfb1d6bc". Symbol was referenced from
fil
e /var/tmp//ccuhlRBW.debug.temp.o
ld: Unsatisfied hidden symbol "btest.c.cfb1d6bc". Symbol was referenced from
fil
e /var/tmp//ccuhlRBW.debug.temp.o
[...]
47 errors.
collect2: fatal error: ld returned 1 exit status
compilation terminated.
make[1]: *** [Makefile:1340: btest_lto] Error 1
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
` (3 preceding siblings ...)
2023-01-06 15:26 ` danglin at gcc dot gnu.org
@ 2023-01-06 17:42 ` cvs-commit at gcc dot gnu.org
2023-01-06 17:44 ` ian at airs dot com
2023-01-06 18:25 ` dave.anglin at bell dot net
6 siblings, 0 replies; 8+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-01-06 17:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>:
https://gcc.gnu.org/g:f3707a55acb980fbcd412ceb980b5621decb4dc0
commit r13-5050-gf3707a55acb980fbcd412ceb980b5621decb4dc0
Author: Ian Lance Taylor <iant@golang.org>
Date: Fri Jan 6 09:39:49 2023 -0800
libbacktrace: don't run --build-id tests if it is not supported
PR libbacktrace/108297
* configure.ac: Test whether linker supports --build-id.
* Makefile.am: Only run --build-id tests if supported.
* configure, Makefile.in: Regenerate.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
` (4 preceding siblings ...)
2023-01-06 17:42 ` cvs-commit at gcc dot gnu.org
@ 2023-01-06 17:44 ` ian at airs dot com
2023-01-06 18:25 ` dave.anglin at bell dot net
6 siblings, 0 replies; 8+ messages in thread
From: ian at airs dot com @ 2023-01-06 17:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Ian Lance Taylor <ian at airs dot com> ---
The LTO problem seems like a different problem, and doesn't seem related to
libbacktrace.
If LTO doesn't work HP/UX, do you have a simple test that the configure script
could run to see whether it works?
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug libbacktrace/108297] libtool link b2test fails: Unrecognized argument: --build-id
2023-01-05 9:00 [Bug libbacktrace/108297] New: libtool link b2test fails: Unrecognized argument: --build-id danglin at gcc dot gnu.org
` (5 preceding siblings ...)
2023-01-06 17:44 ` ian at airs dot com
@ 2023-01-06 18:25 ` dave.anglin at bell dot net
6 siblings, 0 replies; 8+ messages in thread
From: dave.anglin at bell dot net @ 2023-01-06 18:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108297
--- Comment #7 from dave.anglin at bell dot net ---
On 2023-01-06 12:44 p.m., ian at airs dot com wrote:
> If LTO doesn't work HP/UX, do you have a simple test that the configure script
> could run to see whether it works?
Will investigate.
^ permalink raw reply [flat|nested] 8+ messages in thread