public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
@ 2021-12-22 8:20 unlvsur at live dot com
2021-12-22 8:27 ` [Bug libstdc++/103801] " pinskia at gcc dot gnu.org
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: unlvsur at live dot com @ 2021-12-22 8:20 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
Bug ID: 103801
Summary: Link tests are not allowed after GCC_NO_EXECUTABLES.
for pdp11-aout target
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: unlvsur at live dot com
Target Milestone: ---
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... unsupported
checking for shl_load... configure: error: Link tests are not allowed after
GCC_NO_EXECUTABLES.
make[1]: *** [Makefile:13516: configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory
'/home/cqwrteur/myhome/gcc_build/cross/pdp11-aout/gcc'
make: *** [Makefile:1036: all] Error 2
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
@ 2021-12-22 8:27 ` pinskia at gcc dot gnu.org
2021-12-22 11:43 ` unlvsur at live dot com
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-22 8:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Keywords| |build
Last reconfirmed| |2021-12-22
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Did you build newlib along side GCC? Or did you do the two steps of building
GCC with C only and then newlib and then GCC with C++ support?
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
2021-12-22 8:27 ` [Bug libstdc++/103801] " pinskia at gcc dot gnu.org
@ 2021-12-22 11:43 ` unlvsur at live dot com
2021-12-22 11:52 ` unlvsur at live dot com
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: unlvsur at live dot com @ 2021-12-22 11:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
--- Comment #2 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #1)
> Did you build newlib along side GCC? Or did you do the two steps of building
> GCC with C only and then newlib and then GCC with C++ support?
I tried newlib, newlib said it does not support pdp11-aout target anymore.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
2021-12-22 8:27 ` [Bug libstdc++/103801] " pinskia at gcc dot gnu.org
2021-12-22 11:43 ` unlvsur at live dot com
@ 2021-12-22 11:52 ` unlvsur at live dot com
2021-12-22 11:52 ` unlvsur at live dot com
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: unlvsur at live dot com @ 2021-12-22 11:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #1)
> Did you build newlib along side GCC? Or did you do the two steps of building
> GCC with C only and then newlib and then GCC with C++ support?
I suggest removing pdp11 target support if it is so buggy.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
` (2 preceding siblings ...)
2021-12-22 11:52 ` unlvsur at live dot com
@ 2021-12-22 11:52 ` unlvsur at live dot com
2023-07-13 20:16 ` pkoning at gcc dot gnu.org
2023-07-13 20:32 ` pkoning at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: unlvsur at live dot com @ 2021-12-22 11:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
--- Comment #4 from cqwrteur <unlvsur at live dot com> ---
(In reply to cqwrteur from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > Did you build newlib along side GCC? Or did you do the two steps of building
> > GCC with C only and then newlib and then GCC with C++ support?
>
> I suggest removing pdp11 target support if it is so buggy.
remove the entire backend from GCC.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
` (3 preceding siblings ...)
2021-12-22 11:52 ` unlvsur at live dot com
@ 2023-07-13 20:16 ` pkoning at gcc dot gnu.org
2023-07-13 20:32 ` pkoning at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: pkoning at gcc dot gnu.org @ 2023-07-13 20:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
pkoning at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pkoning at gcc dot gnu.org
--- Comment #5 from pkoning at gcc dot gnu.org ---
There is no pdp11 support in newlib (and never was as far as I know; it's not a
matter of it having been "removed"). I've played with creating one, but not
enough to submit the result.
But that doesn't make the pdp11 target meaningless or say it needs to be
removed. The only consequence of the lack of an off the shelf library package
is that you can't run the execution testsuite. But you can, for example, run
the compile part of the testsuite.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libstdc++/103801] Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
` (4 preceding siblings ...)
2023-07-13 20:16 ` pkoning at gcc dot gnu.org
@ 2023-07-13 20:32 ` pkoning at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: pkoning at gcc dot gnu.org @ 2023-07-13 20:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
pkoning at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-07-13 20:32 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-22 8:20 [Bug libstdc++/103801] New: Link tests are not allowed after GCC_NO_EXECUTABLES. for pdp11-aout target unlvsur at live dot com
2021-12-22 8:27 ` [Bug libstdc++/103801] " pinskia at gcc dot gnu.org
2021-12-22 11:43 ` unlvsur at live dot com
2021-12-22 11:52 ` unlvsur at live dot com
2021-12-22 11:52 ` unlvsur at live dot com
2023-07-13 20:16 ` pkoning at gcc dot gnu.org
2023-07-13 20:32 ` pkoning at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).