glibcxx_3.4.9 not found - how to fix?
Charlie Gibbs
flight simulator (see http://www.flightgear.org - a Windows version
is available too). I turned pkgtool loose on the .tgz files and it
happily ground away and installed them - but when I try to run it
with the front-end fgrun, the following messages come out on stderr:
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
fgrun)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgSim.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgViewer.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgGA.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgText.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgDB.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgUtil.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosg.so.54)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libOpenThreads.so.11)
fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/lib/libosgFX.so.54)
Have I entered the Linux version of DLL hell? Presumably it's just a
matter of dropping in some newer libraries, but even after a fair amount
of googling I still can't figure out what to download, where to find it,
or what to do with it once I have it. I'm currently running Slackware
12.0 (kernel 2.6.21.5) - is it time for an upgrade?
Can anyone give me some pointers (e.g. links to tutorials) on how to
deal with Linux library problems?
aTdHvAaNnKcSe...
--
/~\ cgi...@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
Joerg
> I downloaded the Slackware binaries for FlightGear, the
> Linux-based flight simulator (see http://www.flightgear.org - a
> Windows version
> is available too). I turned pkgtool loose on the .tgz files and
> it happily ground away and installed them - but when I try to
> run it with the front-end fgrun, the following messages come out
> on stderr:
>
> fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not
> found (required by fgrun)
<snip>
> Have I entered the Linux version of DLL hell?
In Linux it's called dependency hell ;-) But no, this is a
different case: libstdc++ is one of the main runtime libraries, the
error indicates that the package you've installed was build for a
different slackware version, presumably a more recent one if you
installed the latest version of FlightGear.
> Presumably it's
> just a matter of dropping in some newer libraries, but even
> after a fair amount of googling I still can't figure out what to
> download, where to find it,
You don't want to mess around with libstdc++ unless you know what
you are doing.
> or what to do with it once I have it. I'm currently running
> Slackware 12.0 (kernel 2.6.21.5) - is it time for an upgrade?
>
> Can anyone give me some pointers (e.g. links to tutorials) on
> how to deal with Linux library problems?
>
> aTdHvAaNnKcSe...
>
Get a package for your version, but probably it will be difficult to
get the latest FlightGear for 12.0. You could also look for a
SlackBuild script for 12.0 and build it from source, but you still
need to install some extra libs.
HTH
Joerg
--
For email use g m x d o t n e t
Charlie Gibbs
jstadermann@see_signature.net (Joerg) writes:
> Charlie Gibbs wrote:
>
>> I downloaded the Slackware binaries for FlightGear, the
>> Linux-based flight simulator (see http://www.flightgear.org - a
>> Windows version
>> is available too). I turned pkgtool loose on the .tgz files and
>> it happily ground away and installed them - but when I try to
>> run it with the front-end fgrun, the following messages come out
>> on stderr:
>>
>> fgrun: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not
>> found (required by fgrun)
>
> <snip>
>
>> Have I entered the Linux version of DLL hell?
>
> In Linux it's called dependency hell ;-) But no, this is a
> different case: libstdc++ is one of the main runtime libraries, the
> error indicates that the package you've installed was build for a
> different slackware version, presumably a more recent one if you
> installed the latest version of FlightGear.
Ouch. I've spent my entire career programming well back from the
bleeding edge so we don't get anguished calls like this from customers.
But I guess flight simulators - or games in general - are a different
kettle of fish.
> Get a package for your version, but probably it will be difficult
> to get the latest FlightGear for 12.0. You could also look for a
> SlackBuild script for 12.0 and build it from source, but you still
> need to install some extra libs.
Looks like it's time for an upgrade. I see that Slack 12.2 has been
out for a while, with 13.0 not too far off...
Thanks for the help.
Charlie Gibbs
cgi...@kltpzyxm.invalid (Charlie Gibbs) writes:
> In article <78q87rF...@mid.individual.net>,
> jstadermann@see_signature.net (Joerg) writes:
>
>> Get a package for your version, but probably it will be difficult
>> to get the latest FlightGear for 12.0. You could also look for a
>> SlackBuild script for 12.0 and build it from source, but you still
>> need to install some extra libs.
>
> Looks like it's time for an upgrade. I see that Slack 12.2 has been
> out for a while, with 13.0 not too far off...
>
> Thanks for the help.
Well, I downloaded the .iso for the 12.2 DVD, read the instructions,
and went for it. It went smoothly - but in a fit of foolish
overconfidence I decided to type "reboot" at the root prompt
just to make sure everything was set up OK.
Bad news. The first time, I got the dreaded "LIL" message.
Fortunately, when I cycled the power LILO was happy again.
Booting proceeded right through mounting my partitions.
The next messages to appear on the screen were:
Using /etc/random-seed to initialize /dev/urandom.
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
And that was it. The machine hangs there, no matter how many
times I retry.
Is there anything I can do to diagnose my problem? Or is it time
to repartition the drive and start from scratch? (Thank goodness
I backed up /home and /etc.)
I wish Murphy wrote some of the many installation or upgrade guides
out there. It's all very nice to list the series of steps to do,
but the only mention of what to do if something goes wrong is whatever
the nice people in this group have to offer - I hope. :-)
Charlie Gibbs
cgi...@kltpzyxm.invalid (Charlie Gibbs) writes:
> In article <1805.478T1...@kltpzyxm.invalid>,
> cgi...@kltpzyxm.invalid (Charlie Gibbs) writes:
>
> Well, I downloaded the .iso for the 12.2 DVD, read the instructions,
> and went for it. It went smoothly - but in a fit of foolish
> overconfidence I decided to type "reboot" at the root prompt
> just to make sure everything was set up OK.
>
> Bad news. The first time, I got the dreaded "LIL" message.
> Fortunately, when I cycled the power LILO was happy again.
> Booting proceeded right through mounting my partitions.
> The next messages to appear on the screen were:
>
> Using /etc/random-seed to initialize /dev/urandom.
> Intel ISA PCIC probe: not found.
> Databook TCIC-2 PCMCIA probe: not found.
>
> And that was it. The machine hangs there, no matter how many
> times I retry.
I think I've tracked it down. I booted from the installation DVD,
mounted my hard drive, and examined /var/log/messages. There were
a few more messages, including:
init: open(/dev/console): No such file or directory
Googling for this message brought me to a forum where someone else
had this problem. When he (and I) updated the configuration scripts
in /etc, we forgot to update the ones in /etc/rc.d as well. Once I
did this, the system booted.
Stand down from battle stations.
Charlie Gibbs
Charlie Gibbs
(Charlie Gibbs) writes:
> I think I've tracked it down. I booted from the installation DVD,
> mounted my hard drive, and examined /var/log/messages. There were
> a few more messages, including:
>
> init: open(/dev/console): No such file or directory
>
> Googling for this message brought me to a forum where someone else
> had this problem. When he (and I) updated the configuration scripts
> in /etc, we forgot to update the ones in /etc/rc.d as well. Once I
> did this, the system booted.
I've tracked down and corrected down a couple of other glitches too,
and now my box not only seems to be fully operational, when I tried to
run fgrun (which got me into this mess in the first place) it came up.
And in the end, I've probably come up with the answer to my general
troubleshooting question too. Examine dmesg for error messages -
scan all of /var/log/messages if necessary. (If the system can't
boot far enough to get to a root login, boot from the installation
CD, mount the hard drive, then scan /var/log/messages.) Once you've
found a suspicious error message, type its exact text into google.
It might take some wading through results, but it's amazing what
you can find.
I'll remember that for next time.