https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
Andrew Pinski changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #17 from Nach ---
I just tried my above test case on RHEL6 without an up to date libstdc++ but
with glibc 2.12, and the binary runs just fine.
I double checked my old build system which does not produce these symbols, and
I see it use
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #16 from Andreas Schwab ---
If you want to build for old systems you need to use the old tools from those
old systems and the output will still work on newer systems (backward
compatiblity). New tools are using new features as they ar
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #15 from Richard Biener ---
(In reply to Nach from comment #14)
> (In reply to Richard Biener from comment #13)
> > If you want to target old dynamic linkers then you have to disable support
> > for GCC features that exploit features o
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #14 from Nach ---
(In reply to Richard Biener from comment #13)
> If you want to target old dynamic linkers then you have to disable support
> for GCC features that exploit features of new dynamic linkers. You
> need to rebuild GCC to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #13 from Richard Biener ---
(In reply to Nach from comment #12)
> Isn't the whole point of -static-libstdc++ is to remove the dependency of
> libstdc++ from the binary? Even without the option, it does indeed work fine
> on the system
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #12 from Nach ---
Isn't the whole point of -static-libstdc++ is to remove the dependency of
libstdc++ from the binary? Even without the option, it does indeed work fine on
the system it was compiled on. However, -static-libstdc++ curre
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #11 from Richard Biener ---
(In reply to Nach from comment #10)
> While you may be marking this as invalid, isn't there a serious issue here?
> Shouldn't -static-libstdc++ work without any special flags?
But it works, doesn't it? Tha
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
Nach changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
Richard Biener changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #8 from Marc Glisse ---
gold also produces the unique symbols. Main difference I can think of is
visible in the output of "file test":
ELF 64-bit LSB executable, x86-64, version 1 (SYSV)
ELF 64-bit LSB executable, x86-64, version 1 (GN
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #7 from Nach ---
Upon further testing, -fuse-ld=gold by itself without -Wl,--no-gnu-unique
appears to get the job done.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #6 from Nach ---
> Does compiling with: -fuse-ld=gold -Wl,--no-gnu-unique
> help? Seems like your old system (ld.so?) gets confused by the new feature.
Doing so, there are no longer any "u" symbols appearing with objdump, nor those
li
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #5 from Marc Glisse ---
(In reply to Nach from comment #4)
> The issue isn't that it can't run on a machine with a proper libstdc++
> installed, the issue is that -static-libstdc++ is broken, meaning the binary
> cannot run on a system
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #4 from Nach ---
(In reply to Marc Glisse from comment #3)
> man nm:
>
>"U" The symbol is undefined.
>
>"u" The symbol is a unique global symbol. This is a GNU
> extension [...]
>
> The program does run fine
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #3 from Marc Glisse ---
man nm:
"U" The symbol is undefined.
"u" The symbol is a unique global symbol. This is a GNU extension
[...]
The program does run fine for me with exactly the same compiler on debian.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
--- Comment #2 from Nach ---
(In reply to Richard Biener from comment #1)
> It works for me. What does ldd test show? Do you have the static
> libstdc++/libgcc installed (Debian may package those separately?)
ldd test
linux-gate.so.1 (0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
18 matches
Mail list logo
