Bug#358076: ...
Steve Langasek writes:
> On Wed, Mar 22, 2006 at 04:10:32PM +0100, Christian E. Boehme wrote:
> > You (as in distributor) can solve that problem with using
> > ``--with-gxx-include-dir=/usr/include/c++/4.0'' during configuration
> > as was done with g++-3.4 or tell the GCC people to change their mind
> > about their path resolution policy.
>
> Now that I understand the nature of the bug you're describing, I agree that
> it's a bug and probably should be fixed (though that's left up to the
> package maintainer, not me). It's just not one that anyone else is likely
> to trip over.
hmm, I don't see it as a bug. the nice thing is that you can unpack
old deb's on other places and just use them.
> > > Er, I'm not surprised that trying to invoke g++-4.0 as "g++ -V 3.4" doesn't
> > > work completely. If I run this command, I get link errors as well; if I run
> > > g++-3.4 -Wall simple.c++ -o simple, the program builds and runs fine.
> >
> > Hmm. Wasn't the ``-V'' option specifically introduced for purposes that
> > require a specific compiler version (it's even documented here:
> > http://gcc.gnu.org/onlinedocs/gcc-4.0.3/gcc/Target-Options.html) ?
>
> I have no idea; I'm just not surprised that the various bits of the compiler
> aren't truly interchangeable.
>From the man page:
The -V and -b options work by running the <machine>-gcc-<version>
executable, so there's no real reason to use them if you can just
run that directly.
Reply to: