https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90440
--- Comment #12 from Christian Jullien ---
Using a non-broken ln I have been able to compile gcc 9.1.0 wo other issues on
Solaris 10 sparc.
generated gcc version also passed all the different project I own.
You can close this ticket.
IMHO, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90440
--- Comment #7 from Christian Jullien ---
The Solaris ln bug with 8.31 is described on this ticket:
http://lists.gnu.org/archive/html/bug-coreutils/2019-03/msg00045.html
If it is really the root of the reported issue, gcc is only culprit to not
Assignee: unassigned at gcc dot gnu.org
Reporter: jullien at eligis dot com
Target Milestone: ---
Hi dear maintainers.
For years now, I have been able to compile gcc from last working version.
On my machine, I currently have a fully working gcc/g++ 8.2.0.
Trying to build either 8.3.0 or
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57409
--- Comment #7 from Christian Jullien ---
Thanks for your time on this issue Eric.
My preference goes to PIE failure detection when gcc is bootstrapped and gcc
complains when -pie is set on an unsupported platform.
You can do whatever you want w
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57409
--- Comment #5 from Christian Jullien ---
Thanks,
now all is clear to me.
I see different possible solutions:
1) gcc toolchain detects that it is using a linker that does not support pie
and issue a error "unsupported flag" when we try to use pi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57409
--- Comment #2 from Christian Jullien ---
Thanks for your quick reply yet it is not totally satisfactory.
1) if gcc does not support pie on solaris 10 sparc (I can accept that), gcc
toolchain should detect this and protest (from ./configure) if P
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jullien at eligis dot com
Trying to build recent sudo versions which now uses PIE I got core dumps or
does memory failures since gcc 4.7. It appears the culprit is PIE.
Using 4.8 and all recent gnu
