[Nottingham] Problems compiling - libstdc++

[Michael Simms]

OK, so far we're all making waaaay too many assumptions about what the
problem actually IS.

So, lets go back to basics.

Create the following file as /tmp/blank.cpp

int main()
{
  return 0;
}

then run

g++ /tmp/blank.cpp -o /tmp/blank

does that compile?

type: ldd /tmp/blank

Do you see a line with libstdc++ in it

If so, your g++ compiler is FINE, and so is your libstdc++ and you will
need to look and see why it is failing elsewhere.

If it DOES fail, you have a much simpler example to test to see what is
broken.
-- 
Michael Simms - CEO, Tux Games
http://www.tuxgames.com


On Mon, 2006-05-22 at 09:35 +0100, Peter Aldred wrote:
> On 21/05/06, Martin <martin at ml1.co.uk> wrote:
> > Peter Aldred wrote:
> > [---]
> > >>>System: Mandriva 2006, KDE 3.5.2
> > [---]
> > > [root at peter amarok-1.4.0]
> >
> > Amarok 1.3.1 on KDE 3.4.2 on Mandriva 2006.0 works fine :-)
> >
> > What /have/ you loaded up? Have you got your sources confused by all the
> > cooker stuff?...
> 
> I got KDE 3.5.2 from the SoS repository at seerofsouls.com. Amarok
> 1.3.8 was working ok for me, but I was interested in some of the new
> features in 1.4. If it was an Amarok-only issue I'd go back to 1.3.8
> rather than bear the hassle of sorting this out, but this seems like
> it'd stop me compiling anything in future (though I haven't tried
> anything else).