Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Patch to cast AMD64 perforce-client

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Tony Smith <tony AT smee.org>
  • To: sergey AT optimaltec.com
  • Cc: SM-Discuss <sm-discuss AT lists.ibiblio.org>, Eric Sandall <eric AT sandall.us>
  • Subject: Re: [SM-Discuss] Patch to cast AMD64 perforce-client
  • Date: Wed, 30 Mar 2005 09:50:17 +0100

On Tuesday 29 March 2005 23:05, sergey AT optimaltec.com wrote:
> Guys,
>
> p4 for amd64 requires libstdc++.so.5, but our g++ produces only
> libstdc++.so.6. What do we do? Is this because of g++ 3.4 and not 3.3 in
> test grimoire?

I'd guess that's the case. You should be able to create a symlink to sort it
out.

> Also, why is it different from what p4 for x86 requires? The
> binary for x86 doesn't link to either libstdc++, libm, or libgcc_s, but
> x86_64 one does, according to ldd output.

gcc 3.x requires that when you link a C++ program, you link with g++, and
when
you do so you get a dynamic link to the C++ runtime. gcc 2.95.x was more
lenient about this and you could link with gcc and get a statically linked
C++ runtime.

So, our LINUX24x86 build (see 'p4 -V') is still built with gcc 2.95.3 and is
linked with gcc. Our AMD64 build is built with gcc 3.x and linked with g++,
and hence is dynamically linked to the C++ runtime.

The joys of platform porting :)

Tony




Archive powered by MHonArc 2.6.24.

Top of Page