libstdc issue

libstdc issue

[Koornstra, Reinoud]

Hi Everyone,

I compiled gcc 4.1.2 and installed it.
Compiled swig as well, however, upon starting it give me this:

swig: /lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /lib/libstdc++.so.6)

These libs come included in gcc and I cannot image that such an inconsistency would exist in the gcc source.
Any hints how to resolve this?
Kind Regards,

Reinoud.

Re: libstdc issue

[Ian Lance Taylor]

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> I compiled gcc 4.1.2 and installed it.
> Compiled swig as well, however, upon starting it give me this:
>
> swig: /lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /lib/libstdc++.so.6)
>
> These libs come included in gcc and I cannot image that such an inconsistency would exist in the gcc source.
> Any hints how to resolve this?

gcc does not normally install libgcc_s.so.1 in /lib, so my guess is that
that file came from your OS, and your dynamic linker is finding it
before the libgcc_s.so.1 which was installed by gcc.  You could try
making it a symlink to the libgcc_s.so.1 which you installed.

Note that you can confuse systems by building and installing gcc into
system directories like /lib, overwriting the system libraries and
compilers.  It's often better to install gcc and use it elsewhere.

Ian

RE: libstdc issue

[Koornstra, Reinoud]

Hi Ian,

Thanks for your answer.
Actually I tried to do it like this:

./configure --prefix= --exec-prefix= --enable-languages=c,c++

Hence, I would suspect after the make and make install it would have overwritten any library.
Also also have the gcc in /usr.
However, in ld.so.conf, first /bin is called so I would expect that always first /bin is being searched for any lib.
How to check what versions of gcc libs are installed?
Any hints on repairing this issue?
Kind Regards,

Reinoud.

-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com] 
Sent: Friday, March 06, 2009 5:56 PM
To: Koornstra, Reinoud
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc issue

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> I compiled gcc 4.1.2 and installed it.
> Compiled swig as well, however, upon starting it give me this:
>
> swig: /lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /lib/libstdc++.so.6)
>
> These libs come included in gcc and I cannot image that such an inconsistency would exist in the gcc source.
> Any hints how to resolve this?

gcc does not normally install libgcc_s.so.1 in /lib, so my guess is that
that file came from your OS, and your dynamic linker is finding it
before the libgcc_s.so.1 which was installed by gcc.  You could try
making it a symlink to the libgcc_s.so.1 which you installed.

Note that you can confuse systems by building and installing gcc into
system directories like /lib, overwriting the system libraries and
compilers.  It's often better to install gcc and use it elsewhere.

Ian

which glibc to use

[Koornstra, Reinoud]

Hi Everyone,

I like to use gcc 4.1.2 as compiler version.
Which glibc version can I use with this one?
Glibc 2.9 give me this error:

checking for -z relro option... no
configure: error: linker with -z relro support required

I guess this option is present in a later version of gcc?
Any hints here?
Kind Regards,

Reinoud.

Re: which glibc to use

[Ian Lance Taylor]

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> I like to use gcc 4.1.2 as compiler version.
> Which glibc version can I use with this one?
> Glibc 2.9 give me this error:
>
> checking for -z relro option... no
> configure: error: linker with -z relro support required
>
> I guess this option is present in a later version of gcc?
> Any hints here?

The linker is not part of gcc.  It is part of the GNU binutils.  You
need to use a version of the GNU binutils new enough to support -z
relro.  I think GNU binutils 2.16 or later should work.

Ian

RE: which glibc to use

[Koornstra, Reinoud]

Hi Ian,

Thanks for your answer.
Any other things I need to have before being able to successfully build glibc?
Kind Regards,

Reinoud.

-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com] 
Sent: Monday, March 09, 2009 10:47 PM
To: Koornstra, Reinoud
Cc: gcc-help@gcc.gnu.org
Subject: Re: which glibc to use

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> I like to use gcc 4.1.2 as compiler version.
> Which glibc version can I use with this one?
> Glibc 2.9 give me this error:
>
> checking for -z relro option... no
> configure: error: linker with -z relro support required
>
> I guess this option is present in a later version of gcc?
> Any hints here?

The linker is not part of gcc.  It is part of the GNU binutils.  You
need to use a version of the GNU binutils new enough to support -z
relro.  I think GNU binutils 2.16 or later should work.

Ian

Re: which glibc to use

[Kai Ruottu]

Koornstra, Reinoud wrote:

 > Ian Lance Taylor wrote:
 >
>>> I like to use gcc 4.1.2 as compiler version.
>>> Which glibc version can I use with this one?
>>> Glibc 2.9 give me this error:
>>>
>>> checking for -z relro option... no
>>> configure: error: linker with -z relro support required
>>
>> The linker is not part of gcc.  It is part of the GNU binutils.  You
>> need to use a version of the GNU binutils new enough to support -z
>> relro.  I think GNU binutils 2.16 or later should work.
>> Any other things I need to have before being able to successfully build glibc?

Why do you think you must build glibc?

Are you producing a native or a cross compiler?

If native : Please DON'T try to replace your system glibc!

If cross  : Please use the original glibc for your target,
             DON'T try to replace its system glibc!

gcc options to use

[Koornstra, Reinoud]

Hi,

I am compiling some libs and binaries for core2 duo cpu machines.
The gcc version is 4.3.3 and the arguments I use are:

x86_64-unknown-linux-gnu-gcc -m64 -march=core2 -mtune=core2 bla bla.
When I read the compiled bin with readelf it reports this:

Class: ELF64
Machine: Advanced Micro Devices X86-64
Etc etc.

I guess this is alright....?
Kind Regards,

Reinoud.

Re: gcc options to use

[me22]

On Thu, Mar 19, 2009 at 15:37, Koornstra, Reinoud <koornstra@hp.com> wrote:
>
> I am compiling some libs and binaries for core2 duo cpu machines.
> The gcc version is 4.3.3 and the arguments I use are:
>
> x86_64-unknown-linux-gnu-gcc -m64 -march=core2 -mtune=core2 bla bla.
> When I read the compiled bin with readelf it reports this:
>
> Class: ELF64
> Machine: Advanced Micro Devices X86-64
> Etc etc.
>
> I guess this is alright....?
>

Well readelf would have no idea for which processor the program was
tuned, so it presumably can only report the instruction set, which was
developed by AMD.

Seems alright to me,
~ Scott

Re: which glibc to use

[Ian Lance Taylor]

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> Any other things I need to have before being able to successfully build glibc?

I don't routinely build glibc, so I don't know.  Note that building a
new glibc to replace your system glibc is a job for experts; there are
many subtle issues.  Building a new glibc for a new system is something
handled well by crosstool (http://kegel.com/crosstool).

Ian

RE: which glibc to use

[Koornstra, Reinoud]

Thanks,
I wasn't planning on replacing my current systems glibc, for else many things would break. :-)
I was planning for a glibc for a new system.
Crosstool is very nice, but it's only for older gcc's.

Just wanted to have a gcc and glibc that go well together for a new system.
Any thoughts upon that?
Kind Regards,

Reinoud.

-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com] 
Sent: Wednesday, March 11, 2009 7:03 AM
To: Koornstra, Reinoud
Cc: gcc-help@gcc.gnu.org
Subject: Re: which glibc to use

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> Any other things I need to have before being able to successfully build glibc?

I don't routinely build glibc, so I don't know.  Note that building a
new glibc to replace your system glibc is a job for experts; there are
many subtle issues.  Building a new glibc for a new system is something
handled well by crosstool (http://kegel.com/crosstool).

Ian

RE: libstdc issue

[Koornstra, Reinoud]

Hi,

I got around the issue by doing this:

ln -s /usr/lib/libstdc++.so.6.0.10 /lib/libstdc++.so.6

Now swig doesn't have an issue.
How come it's correctly installed in /usr (./configure --prefix=/usr --exec-prefix=/usr) but not while installing it in /lib?
Kind Regards,

Reinoud.

-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com] 
Sent: Friday, March 06, 2009 5:56 PM
To: Koornstra, Reinoud
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc issue

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> I compiled gcc 4.1.2 and installed it.
> Compiled swig as well, however, upon starting it give me this:
>
> swig: /lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /lib/libstdc++.so.6)
>
> These libs come included in gcc and I cannot image that such an inconsistency would exist in the gcc source.
> Any hints how to resolve this?

gcc does not normally install libgcc_s.so.1 in /lib, so my guess is that
that file came from your OS, and your dynamic linker is finding it
before the libgcc_s.so.1 which was installed by gcc.  You could try
making it a symlink to the libgcc_s.so.1 which you installed.

Note that you can confuse systems by building and installing gcc into
system directories like /lib, overwriting the system libraries and
compilers.  It's often better to install gcc and use it elsewhere.

Ian