Re: GCC 4.7 build problems

Re: GCC 4.7 build problems

[Vincent Diepeveen]

Seems libmpc.so.2 is the file it couldn't find.
I could find it in /usr/local/lib

when i typed
    echo $PATH

then indeed /usr/local/lib wasn't in the path

typed:
   export PATH=/usr/local/lib:$PATH

Went back to /home/install/gcc470 where i had typed previously ../ 
gcc-4.7.0/configure and make
Now typed
    make clean
    make -j8

CRASH

Same error again!

In config.log it says:

/home/install/gcc470/./gcc/cc1: error while loading shared libraries:  
libmpc.so.2: cannot open shared object file or directory : No such  
file or directory

I must set a librarypath maybe, if so, what is its name?

On Apr 15, 2012, at 6:36 PM, Marc Glisse wrote:

> On Sun, 15 Apr 2012, Vincent Diepeveen wrote:
>
>> hi,
>>
>> GCC 4.7.0 is a big step forward! Really a quantumleap.
>>
>> Works great at opensuse 11.3, both i386 and x64 here at AMD64 and  
>> intel Xeon i386 install.
>>
>> Fails to build at OpenSuse 11.2 as well as Scientific Linux 6.2 x64
>>
>> hardware: dual socket Xeon L5420 in both cases.
>>
>> Build error:
>>
>> "configure: error: cannot compute suffix of object files: cannot  
>> compile"
>>
>> Exactly at same spot the same error like at opensuse 11.2
>>
>> The building at Scientific Linux 6.2 x64 is pretty important -  
>> it's the same distro basically like RHEL 6.2
>> SL 6.2 runs a cluster for me. Performance there is crucial.
>>
>> Anyone knows a way how to get it to work there?
>
> http://gcc.gnu.org/wiki/FAQ#Configuration_fails_with_. 
> 27.27configure:_error:_cannot_compute_suffix_of_object_files:_cannot_c 
> ompile.27.27._What_is_the_problem.3F
>
>> Is this the correct list to report build errors?
>
> No, please send any follow-up to gcc-help@gcc.gnu.org only.
>
> -- 
> Marc Glisse

Re: GCC 4.7 build problems

[Marc Glisse]

On Sun, 15 Apr 2012, Vincent Diepeveen wrote:

> Seems libmpc.so.2 is the file it couldn't find.
> I could find it in /usr/local/lib
>
> when i typed
>  echo $PATH
>
> then indeed /usr/local/lib wasn't in the path
>
> typed:
> export PATH=/usr/local/lib:$PATH

That might make sense on windows but not on unix, where libraries and 
executables are separated.

> I must set a librarypath maybe, if so, what is its name?

man ld.so
(really, there are several ways and the best one is for you to chose)

http://gcc.gnu.org/install/configure.html
mentions the name of an environment variable in the paragraph about mpc.

The entry in the FAQ just before the one I referred to gives a simple 
technique to work around this issue.

-- 
Marc Glisse

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 21:46, Marc Glisse wrote:
>
> man ld.so
> (really, there are several ways and the best one is for you to chose)
>
> http://gcc.gnu.org/install/configure.html
> mentions the name of an environment variable in the paragraph about mpc.
>
> The entry in the FAQ just before the one I referred to gives a simple
> technique to work around this issue.

Or read http://gcc.gnu.org/wiki/InstallingGCC

Re: GCC 4.7 build problems

[Vincent Diepeveen]

On Apr 15, 2012, at 10:46 PM, Marc Glisse wrote:

> On Sun, 15 Apr 2012, Vincent Diepeveen wrote:
>
>> Seems libmpc.so.2 is the file it couldn't find.
>> I could find it in /usr/local/lib
>>
>> when i typed
>>  echo $PATH
>>
>> then indeed /usr/local/lib wasn't in the path
>>
>> typed:
>> export PATH=/usr/local/lib:$PATH
>
> That might make sense on windows but not on unix, where libraries  
> and executables are separated.
>
>> I must set a librarypath maybe, if so, what is its name?
>
> man ld.so
> (really, there are several ways and the best one is for you to chose)
>

Thanks once again!

Ok my next attempt after consulting google:

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
though it seemed this variable was empty before.

Crash again, but seemingly other one. Maybe means progress?

Now gives error that i miss gnu/stubs-32.h

Maybe missing ia32libs or something like that not installed. But i  
forgot exact name.
At the ScientificLinux DVD's i cannot find any RPM starting with ia32  
nor libia32.

Tried doing a
    find . | grep "stubs-32.h"

Google gives me advice:
   yum -y glibc-devel

This command doesn't work of course as i'm not on the internet with  
the machine.
On the DVD i found glibc-devel-2.12-1.47.el6.x86_64.rpm

If i click on it, it reports it's already installed.

Also the glibc-headers-2.12-1.47.el6.x86_64.rpm says it's already  
installed.

Any thoughts what i could try?

Thanks in advance,
Vincent

> http://gcc.gnu.org/install/configure.html
> mentions the name of an environment variable in the paragraph about  
> mpc.
>
> The entry in the FAQ just before the one I referred to gives a  
> simple technique to work around this issue.
>
> -- 
> Marc Glisse

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 22:10, Vincent Diepeveen wrote:
>
> Now gives error that i miss gnu/stubs-32.h

You need to install glibc-devel.i686, the 32-bit package.

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 22:13, Jonathan Wakely wrote:
> On 15 April 2012 22:10, Vincent Diepeveen wrote:
>>
>> Now gives error that i miss gnu/stubs-32.h
>
> You need to install glibc-devel.i686, the 32-bit package.

Or just search google for that filename and the first few hits include
several explaining the problem e.g.

http://www.gccupc.org/gcc-upc-faq/article/compiler_build_fails_with_fatal_error_gnu_stubs_32.h_no_such_file_or_directory.html

Re: GCC 4.7 build problems

[Vincent Diepeveen]

Thanks Jonathan!

Google gave me how to add the DVD-rom to the repository, it's  
indexing the 4428 rpm's there now
from the i386 dvd1 of Scientific Linux

Hope it installs the glibc-devel.i868 then and that this solves the  
problem!

On Apr 15, 2012, at 11:13 PM, Jonathan Wakely wrote:

> On 15 April 2012 22:10, Vincent Diepeveen wrote:
>>
>> Now gives error that i miss gnu/stubs-32.h
>
> You need to install glibc-devel.i686, the 32-bit package.

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 22:52, Vincent Diepeveen <diep@xs4all.nl> wrote:
> Thanks Jonathan!
>
> Google gave me how to add the DVD-rom to the repository, it's indexing the
> 4428 rpm's there now
> from the i386 dvd1 of Scientific Linux
>
> Hope it installs the glibc-devel.i868 then and that this solves the problem!

If you don't want to wait you could just grab that RPM, either from
the DVD or the internet, with
wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/updates/security/glibc-devel-2.12-1.47.el6_2.9.i686.rpm

then install it with
yum localinstall glibc-devel-2.12-1.47.el6_2.9.i686.rpm

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 22:59, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 15 April 2012 22:52, Vincent Diepeveen <diep@xs4all.nl> wrote:
>> Thanks Jonathan!
>>
>> Google gave me how to add the DVD-rom to the repository, it's indexing the
>> 4428 rpm's there now
>> from the i386 dvd1 of Scientific Linux
>>
>> Hope it installs the glibc-devel.i868 then and that this solves the problem!
>
> If you don't want to wait you could just grab that RPM, either from
> the DVD or the internet, with
> wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/updates/security/glibc-devel-2.12-1.47.el6_2.9.i686.rpm

Actually to match your existing 64-bit glibc I think that should be

wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/os/Packages/glibc-2.12-1.47.el6.i686.rpm

> then install it with
> yum localinstall glibc-devel-2.12-1.47.el6_2.9.i686.rpm

Re: GCC 4.7 build problems

[Vincent Diepeveen]

hi,

It's not possible to install any of the packages glibc-* from

ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/os/ 
Packages

basically it says each time in so many words the package manager that  
there is a conflict between the same packages i686 and x64,
as of course i'm x64 here.

Is there a way to compile GCC in a manner it doesn't need stubs-32.h,  
as i'm 64 bits here?

Can i compile gcc x64 only somehow?
Would it help if i kick out Java?

In http://gcc.gnu.org/install/configure.html i'm looking there but  
don't know which one to use.



On Apr 16, 2012, at 12:03 AM, Jonathan Wakely wrote:

> On 15 April 2012 22:59, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 15 April 2012 22:52, Vincent Diepeveen <diep@xs4all.nl> wrote:
>>> Thanks Jonathan!
>>>
>>> Google gave me how to add the DVD-rom to the repository, it's  
>>> indexing the
>>> 4428 rpm's there now
>>> from the i386 dvd1 of Scientific Linux
>>>
>>> Hope it installs the glibc-devel.i868 then and that this solves  
>>> the problem!
>>
>> If you don't want to wait you could just grab that RPM, either from
>> the DVD or the internet, with
>> wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/ 
>> i386/updates/security/glibc-devel-2.12-1.47.el6_2.9.i686.rpm
>
> Actually to match your existing 64-bit glibc I think that should be
>
> wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/ 
> i386/os/Packages/glibc-2.12-1.47.el6.i686.rpm
>
>> then install it with
>> yum localinstall glibc-devel-2.12-1.47.el6_2.9.i686.rpm

Re: GCC 4.7 build problems

[Jonathan Wakely]

On 15 April 2012 23:24, Vincent Diepeveen <diep@xs4all.nl> wrote:
> hi,
>
> It's not possible to install any of the packages glibc-* from
>
> ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/os/Packages
>
> basically it says each time in so many words the package manager that there
> is a conflict between the same packages i686 and x64,
> as of course i'm x64 here.

Oops, yes, sorry, you'll need the one from the x86_64 repo:

ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/x86_64/os/Packages/glibc-2.12-1.47.el6.i686.rpm

That's the 32-bit package for 64-bit systems.

> Is there a way to compile GCC in a manner it doesn't need stubs-32.h, as i'm
> 64 bits here?

You could configure GCC with --disable-multilib but I'd suggest
installing the glibc-devel.i686 RPM instead.

Re: GCC 4.7 build problems

[Vincent Diepeveen]

When i try to install this one it says:

"Transaction error

protected multilib versions nss-softoknfreebl-3.12.9-3.el6.i686 !=  
nss-softoknfreebl-3.12.9-11.el6.x86_64"

Not sure what that means
Any thoughts?



On Apr 16, 2012, at 1:19 AM, Jonathan Wakely wrote:

> On 15 April 2012 23:24, Vincent Diepeveen <diep@xs4all.nl> wrote:
>> hi,
>>
>> It's not possible to install any of the packages glibc-* from
>>
>> ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/ 
>> os/Packages
>>
>> basically it says each time in so many words the package manager  
>> that there
>> is a conflict between the same packages i686 and x64,
>> as of course i'm x64 here.
>
> Oops, yes, sorry, you'll need the one from the x86_64 repo:
>
> ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/ 
> x86_64/os/Packages/glibc-2.12-1.47.el6.i686.rpm
>
> That's the 32-bit package for 64-bit systems.
>
>> Is there a way to compile GCC in a manner it doesn't need  
>> stubs-32.h, as i'm
>> 64 bits here?
>
> You could configure GCC with --disable-multilib but I'd suggest
> installing the glibc-devel.i686 RPM instead.

Re: GCC 4.7 build problems

[Vincent Diepeveen]

Trying to compile without multilibs.
Seems to go fine!

In between i see a 3 warnings that stage2 and stage3 have a difference.

but that didn't stop me from doing a make install :)

Thanks!
Vincent

On Apr 16, 2012, at 1:19 AM, Jonathan Wakely wrote:

> On 15 April 2012 23:24, Vincent Diepeveen <diep@xs4all.nl> wrote:
>> hi,
>>
>> It's not possible to install any of the packages glibc-* from
>>
>> ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/ 
>> os/Packages
>>
>> basically it says each time in so many words the package manager  
>> that there
>> is a conflict between the same packages i686 and x64,
>> as of course i'm x64 here.
>
> Oops, yes, sorry, you'll need the one from the x86_64 repo:
>
> ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/ 
> x86_64/os/Packages/glibc-2.12-1.47.el6.i686.rpm
>
> That's the 32-bit package for 64-bit systems.
>
>> Is there a way to compile GCC in a manner it doesn't need  
>> stubs-32.h, as i'm
>> 64 bits here?
>
> You could configure GCC with --disable-multilib but I'd suggest
> installing the glibc-devel.i686 RPM instead.