https://sourceware.org/bugzilla/show_bug.cgi?id=22263
matoro changed:
What|Removed |Added
CC||matoro_bugzilla_glibc@mator
: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: matoro_bugzilla_glibc at matoro dot tk
Target Milestone: ---
65daf5bed68f3e792e80f7c9a12871fd71da32a2 is the first bad commit
commit
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
matoro changed:
What|Removed |Added
CC||matoro_bugzilla_glibc@mator
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
matoro changed:
What|Removed |Added
See Also||https://bugs.gentoo.org/sho
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
matoro changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #2 from matoro ---
(In reply to Nick Clifton from comment #1)
> (In reply to matoro from comment #0)
> Hi Matoro,
>
> > On mips, since this commit, all linking prints the following warning:
> >
> > /usr/lib/gcc/mips64-unknown-lin
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #3 from matoro ---
The warning itself is correct. In golang, CGO_ENABLED=1 (the default) creates
a dynamic exe, while CGO_ENABLED=0 produces a static one.
However the -fPIC part is not accurate. Golang has its own assembly emitt
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #4 from matoro ---
OK, just tested, removing --enable-warn-execstack does resolve the problem.
But that also confirms that toggling that flag is not purely informational, it
has an effect on the linker behavior and causes previous
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #6 from matoro ---
*It's the other way around - CGO_ENABLED=1 is the default, creates a dynamic
binary, and that is the scenario where it is not working. It works with
CGO_ENABLED=0, which creates a static binary, but that is a no
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #8 from matoro ---
(In reply to Nick Clifton from comment #7)
> (In reply to matoro from comment #6)
> Hi Matoro,
>
>
> > Then I compared the scripts with the linker invocations that I got out of
> > pgrep and saw that they were
https://sourceware.org/bugzilla/show_bug.cgi?id=29592
--- Comment #11 from matoro ---
(In reply to Nick Clifton from comment #9)
> (In reply to matoro from comment #8)
>
> Sorry - what I meant was that the problem is not with the code that
> implements the execstack warning, but rather the fact
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: matoro_bugzilla_glibc at matoro dot tk
Target Milestone: ---
Host: sparc64-unknown-linux-gnu
Target: sparc64-unknown-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31998
matoro changed:
What|Removed |Added
CC||matoro_bugzilla_glibc@mator
https://sourceware.org/bugzilla/show_bug.cgi?id=31998
matoro changed:
What|Removed |Added
Resolution|--- |INVALID
URL|
14 matches
Mail list logo