Rick, That configure statement needs to have at least "--enable-__cxa_atexit" added to it, or gcc 3.x won't generate correct code for C++. This was pointed out to me by the guys in Boeblingen almost a year ago. Pointing it out in turn to Patrick Volkerding got me a mention in his Changelog. :)
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Richard Troth Sent: Thursday, February 05, 2004 12:29 PM To: [EMAIL PROTECTED] Subject: Re: compile failures for the 2.4.21 and 2.4.23 kernels > I was afraid of that. Anyone have any tips of how to roll your own GCC rpm > (& glibc & binutils)? I'm feeling the pain of running an unsupported distro. Strictly speaking, you don't need an RPM. And if you're going to "roll your own GCC", as you indicated: # find some space, about 200-300 MB should do wget http://ftp.gnu.org/pub/gnu/gcc/gcc-3.2/gcc-3.2.tar.gz tar xzf gcc-3.2.tar.gz cd gcc-3.2 ./configure --prefix=/usr/local make bootstrap make install The 'make bootstrap' takes a long time, two hours for me, probably longer if you build in an NFS-resident directory. Once the 'make install' has finished, you'll have /usr/local/bin/gcc Enjoy! -- R;
