https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #12 from Andrew Pinski ---
My bet it is due to --enable-version-specific-runtime-libs which does not get
as tested any more.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
Jim Wilson changed:
What|Removed |Added
CC||wilson at gcc dot gnu.org
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #10 from Jakub Jelinek ---
(In reply to Jason Vas Dias from comment #9)
> (In reply to Jakub Jelinek from comment #8)
> > Where do you see -nostdlib being used? I see it neither in your #c0, nor in
> > #c1.
> > Looking at my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #9 from Jason Vas Dias ---
(In reply to Jakub Jelinek from comment #8)
> Where do you see -nostdlib being used? I see it neither in your #c0, nor in
> #c1.
> Looking at my buildlog, -nostdlib is used to link only some libraries,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #8 from Jakub Jelinek ---
Where do you see -nostdlib being used? I see it neither in your #c0, nor in
#c1.
Looking at my buildlog, -nostdlib is used to link only some libraries, like
libstdc++.so.6 itself, or libvtv, libsanitizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #7 from Jason Vas Dias ---
So since I've produced a working Stage3 compiler in the build directory, './',
'./prev-gcc' should be the directory containing the Stage2 gcc build, and
it does in my case, with a config.log :
$ grep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #6 from Jason Vas Dias ---
Yes, Jakub, thanks, I know :
> If you link with g++ or xg++ instead of gcc or xgcc, then the driver is
> adding
> -lstdc++ automatically.
But it is not ME linking, it is the gcc-5.3.0 Makefile.in /
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #4 from Jason Vas Dias ---
Thanks for having a look at this, Richard .
Yes, "some weirdness" is definitely going on -
but I'd like to determine precisely which "weirdness".
This occurred when building my new LFS system's system
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #3 from Richard Biener ---
xg++ from stage1 should already add -lstdc++. Sth else weird is going on for
you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #2 from Jason Vas Dias ---
In fact, it happens for EVERY executable produced by stage2 compiler!
Why is this - do I need to add '-lstdc++' to LDFLAGS or to
--with-stage1-ldflags / --with-boot-ldflags in order to build gcc-5.3.0 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70519
--- Comment #1 from Jason Vas Dias ---
And it happens for gcov also:
/usr/build/linux/gcc-5.3.0/./prev-gcc/xg++
-B/usr/build/linux/gcc-5.3.0/./prev-gcc/ -B/usr/x86_64-pc-linux-gnu/bin/
-nostdinc++
12 matches
Mail list logo
