Bug 4004 – gcc-2.95 atexit() issue

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ethan 2002-06-21 19:11:26 UTC]

On Friday 21 June 2002 09:56, Ethan wrote:

 Sorry if this has been posted before.
 I've found that the gcc-2.95.3 used in the latest PPC build has the
 atexit() problem with static executables (for example, when you build
 fileutils-4.1 with LDFLAGS=-static all execuatbles dump a core).
 If I remember correctly, patches here are required:

 http://sources.redhat.com/ml/libc-alpha/2001-03/msg00140.html

 http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01187.html

 -Ethan

[Comment 1 Mark Guertin 2002-06-23 02:36:15 UTC]

This patch is already applied in gcc-2.95.3-r5 (current build on my PPC box)
from /usr/portage/sys-devel/gcc/files/gcc-2.95.3-atexit.diff

[Comment 2 Ethan 2002-06-23 10:45:00 UTC]

Created attachment 1702 [details]
gcc patch

[Comment 3 Ethan 2002-06-23 10:47:25 UTC]

I see that that patch is applied, but the gcc produced still creates coredumping
static executables.  Use it to build fileutils-4.1 with LDFLAGS=-static and
you'll see what I mean.  The above attachment includes the atexit() fix, and
several other needed fixes for gcc-2.95.3

[Comment 4 Mark Guertin 2002-06-24 16:33:11 UTC]

I've donw what I can do with this and don't want to play in this ebuild too
much, Azarah, can you look at this stuff?

[Comment 5 Martin Schlemmer (RETIRED) 2002-06-29 12:53:17 UTC]

Fixed in gcc-2.95.3-r7.  emerge rsync, then remerge gcc, followed by glibc.

nosferatu src # ./ls TODO
TODO
nosferatu src # ldd ls
	not a dynamic executable
nosferatu src #