Fedora Core 5 x86_64 lib install problems

I’m having issues getting the gnu-radio core libraries installed in the
correct location on my 64-bit installation of Fedora Core 5. The
problem
appears to be the separation of the 32-bit and 64-bit libraries. I
compiled with:
./for-all-dirs …/buildit -n --prefix=$HOME/z.research/z.gnuradio

After compiling gnuradio-core successfully, gr-audio-alsa fails in the
check stage with this error:

make[3]: Entering directory
`/home/matlis/z.research/z.gnuradio/gr-build/gr-audio-alsa/src’
Traceback (most recent call last):
File “./qa_alsa.py”, line 23, in ?
from gnuradio import gr, gr_unittest
File
“/home/matlis/z.research/z.gnuradio/lib/python2.4/site-packages/gnuradio/gr/init.py”,
line 27, in ?
from gnuradio_swig_python import *
File
“/home/matlis/z.research/z.gnuradio/lib/python2.4/site-packages/gnuradio/gr/gnuradio_swig_python.py”,
line 4, in ?
import _gnuradio_swig_python
ImportError: No module named _gnuradio_swig_python
FAIL: run_tests

1 of 1 tests failed

The test routine is looking in …lib/python2.4 - shouldn’t it look in
lib64? This is where _gnuradio_swig_python.so is stored. I noticed
“run_tests” in the gr_audio_alsa/src directory contained the following:

Where to look for installed GNU Radio python modules

FIXME this is wrong on a distcheck. We really need to ask

gnuradio-core

where it put its python files.

installed_pythondir=${prefix}/lib/python2.4/site-packages
installed_pyexecdir=${exec_prefix}/lib64/python2.4/site-packages

I noticed the first line referes to lib as opposed to lib64, but
changing
this to lib64 didn’t seem to fix the problem.

Here are my environment variables defind in .bash_profile:

GR=$HOME/z.research/z.gnuradio
export GR
PATH=$PATH:.:$GR/bin
export PKG_CONFIG_PATH=$GR/lib64/pkgconfig/:/usr/lib64/pkgconfig
export
PYTHONPATH=$GR/lib64/python2.4/site-packages:/usr/lib64/python2.4/site-packages
export LD_LIBRARY_PATH=$GR/lib64
export CVS_RSH=ssh
export LDFLAGS="-L$GR/lib"

Any suggestions?

thanks!

eric


Eric H. Matlis, Ph.D.
Aerospace & Mechanical Engineering Dept.
114 Hessert Center for Aerospace Research
University of Notre Dame
Notre Dame, IN 46556-5684
Phone: (574) 631-7576
Fax: (574) 631-8355

On Fri, Jul 21, 2006 at 10:26:43PM -0400, Eric Hill M. wrote:

Where to look for installed GNU Radio python modules

FIXME this is wrong on a distcheck. We really need to ask gnuradio-core

where it put its python files.

installed_pythondir=${prefix}/lib/python2.4/site-packages
installed_pyexecdir=${exec_prefix}/lib64/python2.4/site-packages

I noticed the first line referes to lib as opposed to lib64, but changing
this to lib64 didn’t seem to fix the problem.

This shouldn’t matter in your case. It’s a warning about
(patholigical) cases where gnuradio-core is installed in a different
prefix than what you’re trying to build. It is strange that the two
path are different however…

export LDFLAGS="-L$GR/lib"

Any suggestions?

Is PYTHONPATH already exported?

Does your system have a /lib64 directory?
Does it contain both 32-bit and 64-bit libraries for at least some
parts?

Eric

On Fri, Jul 21, 2006 at 09:29:00PM -0700, Eric B. wrote:

(patholigical) cases where gnuradio-core is installed in a different
prefix than what you’re trying to build. It is strange that the two
path are different however…

Answering my own query… The two lines should be different. One is
the library path (which has the lib64), the other is the “execpath”.

Eric

On Fri, Jul 21, 2006 at 10:26:43PM -0400, Eric Hill M. wrote:

`/home/matlis/z.research/z.gnuradio/gr-build/gr-audio-alsa/src’
import _gnuradio_swig_python
ImportError: No module named _gnuradio_swig_python
FAIL: run_tests

1 of 1 tests failed

Eric,

I just tried this on my X86_64 running SuSE 9.3. Worked fine for me
on a fresh checkout from CVS. The output of

$ ./for-all-dirs …/buildit --prefix=/home/eb/test/install 2>&1 | tee
make.log

is here: http://comsec.com/make.log

Perhaps you can figure out what’s different between the two runs?
I suggest examining the output of configure for gnuradio-core and
gr-audio-alsa. I didn’t set any environment variables to special
values. I just used buildit and the normal values I use for building
with the default prefix (/usr/local).

Here are my tool versions:

$ uname -a
Linux dee 2.6.11.4-21.12-smp #1 SMP Wed May 10 09:38:20 UTC 2006 x86_64
x86_64 x86_64 GNU/Linux

$ g++ --version
g++ (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux)

$ autoconf --version
autoconf (GNU Autoconf) 2.59

$ automake --version
automake (GNU automake) 1.9.5

$ libtool --version
ltmain.sh (GNU libtool) 1.5.14 (1.1220.2.195 2005/02/12 12:12:33)

Environment variables:

PYTHONPATH=/usr/local/lib64/python2.4/site-packages:/home/eb/dtools/python
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:/usr/local/lib/pkgconfig:/usr/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig

I do NOT have LD_LIBRARY_PATH set.

FYI, I removed all GNU Radio stuff from /usr/local/* before doing this
build
with the non-default prefix.

Eric

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs