Unusual error message from gcc34 ?

[walt]

Joerg Sonnenberger wrote:
On Sun, Jul 04, 2004 at 12:53:07PM -0700, walt wrote:

Matthew Dillon wrote:


  If everything is brought up to date (you cvsup, buildworld, 
  installworld,
  and make upgrade), and you then rebuild libtool, it should no longer 
  fail
  on crtbegin/end when you switch compilers...
Correct -- now it fails with missing C++ symbols when I switch compilers.


That's not surprising, because GCC 2.95, 3.0, 3.2 and 3.3 changed the ABI
for C++.
What still *does* surprise me is that Hiten (early in this thread) said that
he compiled the aspell port with both compilers and had no problem.  I still
am not sure whether I have a problem on my own machine which needs to be
fixed -- or if this really is a problem with 'libtool' which everyone has,
and not just me.
Does 'libtool' really lock the end-user into using the same compiler all
the time, or am I doing something wrong (on both DFly and NetBSD)?
I'm not pestering you to fix a broken port -- I'm just trying to educate
myself.
Thanks!