I tried yesterday. During the install it yacks at trying to install the application server that comes with Java Studio Creator. Complains about lacking libstdc++ or compat-libstdc++ or something like that. Anyone see this or know what to do about it?
I ask here in case there is some trick to getting a piece of software (that's obviously looking for one version of libstdc++) to see what's installed. According to this page (http://developers.sun.com/prodtech/javatools/jscreator/reference/docs/StartH...) it works with RHEL 2.1. What changed so drastically in this regard between there and here?
Preston
On Sat, 2005-12-10 at 09:01 -0800, Preston Crawford wrote:
What changed so drastically in this regard between there and here?
Preston
Other than the Kernel and version of GCC?
:-)
Yes, I know things have changed. Just unsure (not being a systems guy) why it wouldn't see the newer version of libstdc++ and be fine with it.
Preston
Preston Crawford wrote:
On Sat, 2005-12-10 at 09:01 -0800, Preston Crawford wrote:
What changed so drastically in this regard between there and here?
Preston
Other than the Kernel and version of GCC?
:-)
Yes, I know things have changed. Just unsure (not being a systems guy) why it wouldn't see the newer version of libstdc++ and be fine with it.
Preston
You could create a softlink with a different version number to see if the app stops complaining. This sometimes fixes little issues like that, but it's not the most elegant way I know.
You can destroy the symlink if that doesn't help.
HTH
Alex
On Sat, 2005-12-10 at 11:35 -0600, Alex White wrote:
Preston Crawford wrote:
On Sat, 2005-12-10 at 09:01 -0800, Preston Crawford wrote:
What changed so drastically in this regard between there and here?
Preston
Other than the Kernel and version of GCC?
:-)
Yes, I know things have changed. Just unsure (not being a systems guy) why it wouldn't see the newer version of libstdc++ and be fine with it.
Preston
You could create a softlink with a different version number to see if the app stops complaining. This sometimes fixes little issues like that, but it's not the most elegant way I know.
You can destroy the symlink if that doesn't help.
What would I be symlinking to?
Preston
Preston Crawford wrote:
On Sat, 2005-12-10 at 11:35 -0600, Alex White wrote:
Preston Crawford wrote:
On Sat, 2005-12-10 at 09:01 -0800, Preston Crawford wrote:
What changed so drastically in this regard between there and here?
Preston
Other than the Kernel and version of GCC?
:-)
Yes, I know things have changed. Just unsure (not being a systems guy) why it wouldn't see the newer version of libstdc++ and be fine with it.
Preston
You could create a softlink with a different version number to see if the app stops complaining. This sometimes fixes little issues like that, but it's not the most elegant way I know.
You can destroy the symlink if that doesn't help.
What would I be symlinking to?
Preston
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
[prata@crane ~]$ ls -la /usr/lib/libstdc++.so. libstdc++.so.5 libstdc++.so.6 libstdc++.so.5.0.7 libstdc++.so.6.0.3
(this is what results display when I tab /usr/lib/libstdc++.so.)
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
This would fake the app out if it's just lookin' for a library with that name, as some apps tend to do.
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
HTH
Alex White
On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote:
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
Okay, I wasn't sure which one I'd symlink off of. I appreciate the explanation.
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
I need to look at the error log. It might be looking in an entirely different location, maybe? I mean either it's hard-coded to look for a certain version or to look somewhere else (assuming it's possible that RHEL 2.x ut libstdc somewhere else).
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
:-)
Thanks.
Preston
On 12/10/05, Preston Crawford me@prestoncrawford.com wrote:
On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote:
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
Okay, I wasn't sure which one I'd symlink off of. I appreciate the explanation.
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
I need to look at the error log. It might be looking in an entirely different location, maybe? I mean either it's hard-coded to look for a certain version or to look somewhere else (assuming it's possible that RHEL 2.x ut libstdc somewhere else).
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
:-)
Thanks.
Instead of wrecking systems with random symlinks trying to meet compatible versions of things, why not do "yum provides filename" and see if it is available to you.
yum list "compat*" yeilds several packages that might be what you're looking for.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Sat, 2005-12-10 at 13:08 -0500, Jim Perrin wrote:
Instead of wrecking systems with random symlinks trying to meet compatible versions of things, why not do "yum provides filename" and see if it is available to you.
yum list "compat*" yeilds several packages that might be what you're looking for.
You learn something every day. I had never used that command. Thanks.
That yielded compat-libstdc++-296.i386.
Is that something you can install along side the other compat-libstdc++- X versions without any harm to the system?
Also, and I know this may be headed into "best practices territory" what is the preferred method? To install libraries you don't need because someone hard-coded a reference to a library or to just do the symlink. That's not meant to be rhetorical or flippant. I really am curious and not sure which approach is best practice.
Thanks for the tip either way, though.
Preston
Jim Perrin wrote:
On 12/10/05, Preston Crawford me@prestoncrawford.com wrote:
On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote:
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
Okay, I wasn't sure which one I'd symlink off of. I appreciate the explanation.
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
I need to look at the error log. It might be looking in an entirely different location, maybe? I mean either it's hard-coded to look for a certain version or to look somewhere else (assuming it's possible that RHEL 2.x ut libstdc somewhere else).
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
:-)
Thanks.
Instead of wrecking systems with random symlinks trying to meet compatible versions of things, why not do "yum provides filename" and see if it is available to you.
yum list "compat*" yeilds several packages that might be what you're looking for.
Thank you for clearing that little bit up. Because you know..I've destroyed numerous machines in my career over a single app. *blinkles*
Alex White
On Sat, 2005-12-10 at 13:03 -0600, Alex White wrote:
Thank you for clearing that little bit up. Because you know..I've destroyed numerous machines in my career over a single app. *blinkles*
Alex White
Uh oh! Here we go.
*Ding!* *Ding!*
Preston
On 12/10/05, Alex White ethericalzen@gmail.com wrote:
Jim Perrin wrote:
On 12/10/05, Preston Crawford me@prestoncrawford.com wrote:
On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote:
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
Okay, I wasn't sure which one I'd symlink off of. I appreciate the explanation.
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
I need to look at the error log. It might be looking in an entirely different location, maybe? I mean either it's hard-coded to look for a certain version or to look somewhere else (assuming it's possible that RHEL 2.x ut libstdc somewhere else).
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
:-)
Thanks.
Instead of wrecking systems with random symlinks trying to meet compatible versions of things, why not do "yum provides filename" and see if it is available to you.
yum list "compat*" yeilds several packages that might be what you're looking for.
Thank you for clearing that little bit up. Because you know..I've destroyed numerous machines in my career over a single app. *blinkles*
Alex White
eh. I hadn't planned on starting up another mailing list pissing match here, nor do I feel like engaging in one. Ask any 8 administrators how to do something and you'll get 9 ways to do it. Yes, your way may well work, and you may be happy with that. But what happens down the road for the next app and the app after that? Instead of symlinking newer libs to older lib names, why not simply see if you have the older lib available to you? That was my whole point. What happens when you create this type of symlink to a file you later install via yum? Even if you're aware of little tweaks like this and they work but they're not the absolute pristine ivory tower elitist way to solve things, it's possible the person asking on the list may not know any better, and for subsequent apps may get link happy.
Yes. Your way works and probably well, but it's not ivory tower quality advice for people still learning. I teach best practice type things on a daily basis, and I make every effort to carry that into what I post for help on the list.
/last comment //will not continue this thread ///implore others not to let this thread grow to the absurd lengths of others.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
Jim Perrin wrote:
On 12/10/05, Alex White ethericalzen@gmail.com wrote:
Jim Perrin wrote:
On 12/10/05, Preston Crawford me@prestoncrawford.com wrote:
On Sat, 2005-12-10 at 11:46 -0600, Alex White wrote:
Well libstdc++ exists in /usr/lib/ on my system 4 U2 it's:
Okay, I wasn't sure which one I'd symlink off of. I appreciate the explanation.
Now, if you know that your application is erroring off with something similar to "unable to locate libstdc++.so.2" Just as an example, then you could do something like: ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc.so.2
I need to look at the error log. It might be looking in an entirely different location, maybe? I mean either it's hard-coded to look for a certain version or to look somewhere else (assuming it's possible that RHEL 2.x ut libstdc somewhere else).
If that doesn't work then just delete your symlink and all will be right with the world. Make sure not to delete the actual library though, I've done somethin' stupid like that before lol
:-)
Thanks.
Instead of wrecking systems with random symlinks trying to meet compatible versions of things, why not do "yum provides filename" and see if it is available to you.
yum list "compat*" yeilds several packages that might be what you're looking for.
Thank you for clearing that little bit up. Because you know..I've destroyed numerous machines in my career over a single app. *blinkles*
Alex White
eh. I hadn't planned on starting up another mailing list pissing match here, nor do I feel like engaging in one. Ask any 8 administrators how to do something and you'll get 9 ways to do it. Yes, your way may well work, and you may be happy with that. But what happens down the road for the next app and the app after that? Instead of symlinking newer libs to older lib names, why not simply see if you have the older lib available to you? That was my whole point. What happens when you create this type of symlink to a file you later install via yum? Even if you're aware of little tweaks like this and they work but they're not the absolute pristine ivory tower elitist way to solve things, it's possible the person asking on the list may not know any better, and for subsequent apps may get link happy.
Yes. Your way works and probably well, but it's not ivory tower quality advice for people still learning. I teach best practice type things on a daily basis, and I make every effort to carry that into what I post for help on the list.
/last comment //will not continue this thread ///implore others not to let this thread grow to the absurd lengths of others.
Discussed off list and resolved.
Excuse the waste of bandwidth.
Alex White
Okay, got the answer in case anyone needs it in the future.
BTW, doesn't Sun also develop a Unix OS? I mean....???? WTH?
http://blogs.sun.com/roller/page/david? entry=installing_creator_on_ubuntu_linux
There's where I found my help.
Here's the command I ran.
ln -s /usr/lib/libstdc++.so.5 /usr/lib/libstdc++-libc6.2-2.so.3
Yes, you have to name the symlink EXACTLY that.
Ahhhhhh.....
Anyway.
Preston
-
Alex White -
Jim Perrin -
Preston Crawford