[lokisetup] gcc 3.2
ttimo at idsoftware.com
Mon Dec 9 19:12:16 EST 2002
Yes, C++ ABI between GCC 2.x and 3.x changes. It's likely that 3.x-based
systems will need specific binaries as soon as there's some linking to
shared library involving C++.
For instance, Debian Sid is still 2.x based, if you try to compile some
software using libsig++ with 3.x on there, it won't link against system
provided libsig++ because of ABI issues.
I would suppose that if you statically link all those crappy C++ libraries
you should be able to distribute 3.x-built binaries to 2.x distros..
On Mon, 9 Dec 2002 19:07:47 -0500
Chunky Kibbles <chunky at icculus.org> wrote:
> On Mon, Dec 09, 2002 at 04:04:51PM -0800, Stephane Peter wrote:
> > On Mon, 2002-12-09 at 16:00, Troy A. Griffitts wrote:
> > > Hey guys. I'm new to the list and wanted to get some key insights from
> > > people who are 'in the know' with all the cool features that have been
> > > added to setup lately.
> > >
> > > 1) Is there a way to detect a gcc 3.2 system now? And a place for binaries?
> > Not directly. You may be able to detect it through scripts, but I can
> > hardly see how this would be helpful. Binaries should not depend on a
> > particular version of gcc...
> As in, the binaries that you're distributing as part of your program
> that's being installed.
> Currently, for eg, I've heard of problems with my UnrealI stuff from
> people who're on GCC 3 Systems; they essentially require a different
> Gary (-;
More information about the Lokisetup