Hey Tim, Was able to make it past the libiberty issue. I ended up downloading another tar of GCC. Now it does a partial fail when I do a gmake install. Here is the error I'm getting; Gmake[4] *** [install-headers] error 1 Gmake[4] leaving directory '/tmp/gcc-4.1.1/objsrc/build-sparc-sun-solaris2.10/libstdc++-V3/include' Gmake[3] *** [install-am] Error 2 Gmake[3] leaving directory '/tmp/gcc-4.1.1/objsrc/build-sparc-sun-solaris2.10/libstdc++-V3/include' Gmake[2] *** [install-recursive] error 1 Gmake[2] leaving directory '/tmp/gcc-4.1.1/objsrc/build-sparc-sun-solaris2.10/libstdc++-V3 Gmake[1] *** [install-target-libstdc+++-V3] Error 2 Gmake[1] leaving directory '/tmp/gcc-4.1.1/objsrc/ Gmake: *** [install] Error 2 It creates the GCC directory structure and creates the compiled versions of gcc, c++, etc but it didn't create the libstdc++ files for c++. The gcc file seems to work since I was able to compile a file. My configure command is the following; ../configure --prefix=/opt/gcc-4.1.1 --enable-languages=c,c++ Matt -----Original Message----- From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx] On Behalf Of Tim Prince Sent: Tuesday, May 24, 2016 8:02 PM To: gcc-help@xxxxxxxxxxx Subject: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation On 5/24/2016 12:35 PM, Joseph, Matthew wrote: > Hello, > > I'm trying to build GCC 4.1.1 on a Solaris 10 Update 8 box but I'm running into an issue stating that libiberty.a: No such file or directory. > Here is some information. > > cd /tmp/gcc4.1.1/objsrc/ > /tmp/gcc-4.1.1/configure -prefix=/opt/gcc-4.1.1 -enable-languages=c,c++ --build=sparc-sun-solaris2.10 > gmake all-gcc > > gcc -g -02 -o fixincl finxcl.o fixtests.o fixfixes.o server.o procopen.o fixlib.o fixopts.o ../libiberty/libiberty.a > gcc: ../libiberty/libiberty.a: No such file or directory > gmake[1] *** [full-stamp] Error 1 > gmake[1] Leaving directory '/tmp/gcc-4.1.1/objsrc/build-sparc-sun-solaris2.10/fixincludes' > gmake: *** [all-build-fixincludes] Error 2 > > What I did was copy the libiberty.a from /usr/sfw/lib/ into gcc-4.1.1/libiberty/ directory when I first started getting this error but that didn't help remedy this issue. > > If anyone could help me with this issue that would be great. > If you need more information please let me know. > > Thanks, > > Matt > Did you try cd'ing into libiberty build directory at this point, then what happens when you run libiberty/configure and make? If you aren't trying to make a cross compiler you shouldn't need to specify --build in your original configure. -- Tim Prince
