Date: Thu, 6 May 1999 10:59:37 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Mark Ovens <marko@uk.radan.com> Cc: FreeBSD-questions <questions@FreeBSD.ORG> Subject: Re: gcc differences between aout & ELF Message-ID: <Pine.BSF.4.03.9905061058240.25986-100000@resnet.uoregon.edu> In-Reply-To: <19990505235002.C2189@marder-1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 May 1999, Mark Ovens wrote: > On Wed, May 05, 1999 at 02:15:41PM -0700, Doug White wrote: > > On Tue, 4 May 1999, Mark Ovens wrote: > > > > > > > Should I expect there to be any differences between the same version > > > > > of gcc under 2.2.8 and 3.1, other than one outputting aout files and > > > > > the other outputting ELF?. > > > > > > > > > > I have a (large) program that compiled and linked fine using gcc 2.8.1 > > > > > (*not* the standard gcc used for building the system). After u/g to > > > > > 3.1 this program wouldn't run as some of the required aout libs are > > > > > not installed. I installed gcc-2.8.1 from the packages on the 3.1 CD > > > > > and recompiled my program but I get errors, mainly from the linker > > > > > (undefined symbols etc). > > > > Why don't you rebuild the required libraries to ELF? > > Why should I have too? This system was installed from scratch, it's > all ELF (I've file(1)'d all the libs I can find and they're all > ELF, except the aout compat stuff). Because you can't link aout libs into an elf binary. > I think I may know what I've screwed up. Before I installed gcc-2.8.1 > I tried egcs-1.1.1. That gave more errors, so I then installed > gcc-2.8.1. I've since read some docs at Cygnus' website that mention > that egcs includes a new libstdc++ (?) whereas gcc-2.8.1 doesn't. > Also pkg_info -v egcs-1.1.1 mentioned something about moving some > libs "to avoid conflict with the stock compiler". I've pkg_deleted > both egcs and gcc and the re-installed gcc. I'm now re-compiling > my job (it'll take about 1-1/4 hours to compile the ~6000 source > files) so I'm keeping my fingers crossed that it'll work this time. Yeah, stdc++ will muck things up badly. They're still playing with it on -CURRENT. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9905061058240.25986-100000>