I am a Linux newbie trying to install wxPython 2.5.1.5 using the .rpm. I resolved failed
dependencies for libexpat and SDL by downloading and installing
packages. But those shown below remain.
What is wanted by "/usr/bin/python"?
What does the "(GLIBC_2.3)" of "libc.so.6(GLIBC_2.3) " mean?
I tried installing glib from links to .rpm from Migration Guide
but no joy (installed OK, but no dependency was removed.)
Thanks for reading this far and any help.
···
------------------------------------------------------------------------------------
bash-2.05# rpm -i wxPythonGTK-py2.3-2.5.1.5-1.i386.rpm
error: failed dependencies:
/usr/bin/python is needed by wxPythonGTK-py2.3-2.5.1.5-1
libc.so.6(GLIBC_2.3) is needed by wxPythonGTK-py2.3-2.5.1.5-1
libgcc_s.so.1 is needed by wxPythonGTK-py2.3-2.5.1.5-1
libgcc_s.so.1(GCC_3.0) is needed by wxPythonGTK-py2.3-2.5.1.5-1
libgcc_s.so.1(GLIBC_2.0) is needed by wxPythonGTK-py2.3-2.5.1.5-1
libpthread.so.0(GLIBC_2.3.2) is needed by wxPythonGTK-py2.3-2.5.1.5-1
libstdc++.so.5 is needed by wxPythonGTK-py2.3-2.5.1.5-1
libstdc++.so.5(CXXABI_1.2) is needed by wxPythonGTK-py2.3-2.5.1.5-1
libstdc++.so.5(GLIBCPP_3.2) is needed by wxPythonGTK-py2.3-2.5.1.5-1
I am a Linux newbie trying to install wxPython 2.5.1.5 using the .rpm. I
resolved failed
dependencies for libexpat and SDL by downloading and installing
packages. But those shown below remain.
What is wanted by "/usr/bin/python"?
The install is looking for a file called /usr/bin/python. When you do an
'rpm -q python', what do you get? How about a 'which python'?
The other files might be resolved by the installation of the python rpm,
but I haven't checked that. I often find that www.rpmfind.org is the place
to go because they give links to the required supporting stuff. Post the
output of the above commands, and I'll help you work it out.
--vicki
"A pessimist sees the difficulty in every opportunity; an optimist sees
the opportunity in every difficulty."
-- Winston Churchill
Vicki Stanfield wrote:
I am a Linux newbie trying to install wxPython 2.5.1.5 using the .rpm. I
resolved failed
dependencies for libexpat and SDL by downloading and installing
packages. But those shown below remain.
What is wanted by "/usr/bin/python"?
The install is looking for a file called /usr/bin/python. When you do an
'rpm -q python', what do you get? How about a 'which python'?
bash-2.05# rpm -q python
package python is not installed
bash-2.05# which python
/usr/bin/python
I didn't install python with an .rpm but by downloading the source
and compiling it. Rpm saying it is not installed means it is not
installed as a redhat package?
The other files might be resolved by the installation of the python rpm,
but I haven't checked that. I often find that www.rpmfind.org is the place
to go because they give links to the required supporting stuff. Post the
output of the above commands, and I'll help you work it out.
--vicki
"A pessimist sees the difficulty in every opportunity; an optimist sees
the opportunity in every difficulty."
-- Winston Churchill
Thanks Vicki!
Vicki Stanfield wrote:
I am a Linux newbie trying to install wxPython 2.5.1.5 using the .rpm.
I
resolved failed
dependencies for libexpat and SDL by downloading and installing
packages. But those shown below remain.
What is wanted by "/usr/bin/python"?
The install is looking for a file called /usr/bin/python. When you do an
'rpm -q python', what do you get? How about a 'which python'?
bash-2.05# rpm -q python
package python is not installed
bash-2.05# which python
/usr/bin/python
I didn't install python with an .rpm but by downloading the source
and compiling it. Rpm saying it is not installed means it is not
installed as a redhat package?
Thanks Vicki!
Any particular reason that you are using rpm now and didn't then? I see
three courses of action:
1) install the python rpm and see what dependencies are left
2) investigate that the other dependencies are actually met by looking
over the remaining complaints from rpm, and once you are convinced that
everything is there and is where it should be, force the rpm install
3) install wxPython from source too
--vicki
"A pessimist sees the difficulty in every opportunity; an optimist sees
the opportunity in every difficulty."
-- Winston Churchill
Vicki Stanfield wrote:
Vicki Stanfield wrote:
I am a Linux newbie trying to install wxPython 2.5.1.5 using the .rpm.
I
resolved failed
dependencies for libexpat and SDL by downloading and installing
packages. But those shown below remain.
What is wanted by "/usr/bin/python"?
The install is looking for a file called /usr/bin/python. When you do an
'rpm -q python', what do you get? How about a 'which python'?
bash-2.05# rpm -q python
package python is not installed
bash-2.05# which python
/usr/bin/python
I didn't install python with an .rpm but by downloading the source
and compiling it. Rpm saying it is not installed means it is not
installed as a redhat package?
Thanks Vicki!
Any particular reason that you are using rpm now and didn't then? I see
three courses of action:
1) install the python rpm and see what dependencies are left
2) investigate that the other dependencies are actually met by looking
over the remaining complaints from rpm, and once you are convinced that
everything is there and is where it should be, force the rpm install
3) install wxPython from source too
--vicki
"A pessimist sees the difficulty in every opportunity; an optimist sees
the opportunity in every difficulty."
-- Winston Churchill
I am downloading the python rpm as I type. I didn't install from it originally
because I didn't know it existed. (I missed the Linux Rpms link in the sidebar.)
I didn't install wxPython from the source because the description of what was
involved made my eyes water.
If I force RPM to install wxPython's rpm, no real harm will be done if it fails?
Thanks muchly for your help.
DogWalker wrote:
If I force RPM to install wxPython's rpm, no real harm will be done if it fails?
no harm, it just might not work.
However, your other dependency failures look like system libraries. I suspect that you are using an older system that Robin built the rpm on. You might try to build the source rpm, which is easier than building the source tarball. I couldn't get it to work with RedHat 7.2 (which is three years old, to be fair), so I've build from the tar ball. It's not too bad, just follow the directions.
You might search the system for some of those libraries it's looking for, it will give you hint as to what the problem is. In particular, look for older versions of the same libs. If you have them, you're on an older system, and you'll need to build.
-Chris
···
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
Chris Barker wrote:
DogWalker wrote:
If I force RPM to install wxPython's rpm, no real harm will be done if it
fails?
no harm, it just might not work.
However, your other dependency failures look like system libraries. I
suspect that you are using an older system that Robin built the rpm on.
You might try to build the source rpm, which is easier than building the
source tarball. I couldn't get it to work with Red Hat 7.2 (which is
three years old, to be fair), so I've build from the tar ball. It's not
too bad, just follow the directions.
You might search the system for some of those libraries it's looking
for, it will give you hint as to what the problem is. In particular,
look for older versions of the same libs. If you have them, you're on an
older system, and you'll need to build.
-Chris
I have SuSE 7.2. I also have wxPythonSrc-2.5.1.5 untarred. I think that I'll try
to build it from Robin's instructions. I can get whatever glib+gtk+gcc
libraries remain the old-fashioned way: my system may be more
comprehendible that way. (The python rpm had failed dependencies, too.
Perhaps a Red Hat thing.)
Thanks Chris and Vicki.
I have SuSE 7.2. I also have wxPythonSrc-2.5.1.5 untarred. I think that
I'll try
to build it from Robin's instructions. I can get whatever glib+gtk+gcc
libraries remain the old-fashioned way: my system may be more
comprehendible that way. (The python rpm had failed dependencies, too.
Perhaps a Red Hat thing.)
Thanks Chris and Vicki.
Oh, I thought you said RedHat. Well, no matter, I have a SuSE system as
well, so if you have further trouble, just post it and I'll be happy to
try to help.
--vicki
"A pessimist sees the difficulty in every opportunity; an optimist sees
the opportunity in every difficulty."
-- Winston Churchill