Re: [Discuss-gnuradio] Instaling Baseline requirment problem
As requested, the build sample information has been updated: http://www.kd7lmo.net/ground_gnuradio_baseline.html On Tue, 20 Sep 2005, Eric Blossom wrote: > On Tue, Sep 20, 2005 at 12:18:10PM +, Robert McGwier wrote: > > Same here: > > > > Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not > > compile. The latest version, 2_7_0 gets further into the build than > > before but will not build. Since I could not figure out a single need > > for it, I removed it from KD7LMO's baseline build stuff. > > > > Please let me pass along a warning. A month ago, I upgraded gcc and > > got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and > > remake wxPython 2.6.1 in an abortive attempt to get beyond some of this > > "coloring with Crayola crayon and finger painting" look with improperly > > initialized controls/broken controls, etc. have in wxGtk/wxPython. > > WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to > > work since. I have been completely dead in the water, unable to > > diagnose what was wrong other than import wx gave me "undefined symbols > > in pango" even after I went backwards. I finally just pulled off my > > personal files and rebuilt the distribution and used the wxGtk that came > > with SUSE. I admit I had other things going on during that month that > > interfered (the month from just north of the river Styx), but this was a > > painful reminder of the old addage" if it ain't broke, don't fix it > > unless you want to stall development. > > > > Bob > > Good points. > > KD7LMO, can you please remove xerces from your build instructions? > Not sure what program uses it, but it's not one of ours. > > Thanks, > Eric > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 08:26:31PM -0700, Eric Blossom wrote: > > All the modules that depend on gnuradio-core use pkg-config to > locate the gnuradio-core library and includes at configure time. > Which one it finds is dependent on the setting of the PKG_CONFIG_PATH > environment variable. My environment variables which refer to /usr/gr/local are these: PATH=/usr/gr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/gr/bin GR_PREFIX=/usr/gr/local PKG_CONFIG_PATH=/usr/gr/local/lib/pkgconfig PYTHONPATH=/usr/gr/local/lib/python2.4/site-packages LD_LIBRARY_PATH=/usr/gr/local/lib > If you're installing gnuradio-core in /usr/gr/local, then you'll find > that it installs a file: /usr/gr/local/lib/pkgconfig/gnuradio-core.pc Indeed it does. > The other gr-* packages need a way to find that file. They do that > through the PKG_CONFIG_PATH environment variable. It wants to contain > the path to that directory, and perhaps /usr/local/lib/pkgconfig too (or > whereever fftw3f.pc was installed.) That is the case. fftw3f.pc seems to be found even though that path is not part of PKG_CONFIG_PATH in my variable. Buildit sets PKG_CONFIG_PATH with both paths and apparently works in most cases. For some reason, I still need it in my environment for everything to build. > The great thing about pkg-config is that it keeps you from having to > guess about what -I, -L and -l options you need to use to compile > and link a tool that uses a given package. That seems to work except for the usrp build. The libusb include and lib files are not found in /usr/local but there is no libusb.pc file there either. This is the FreeBSD port of libusb-0.1.10a which I'm not sure is right but it does compile with the usrp code. > Note: for some reason, the command is called pkg-config, but the RPM, > library path and distribution tarball is called pkgconfig. Of course, I'm using FreeBSD so it is not an RPM but a FreeBSD "port". pkgconfig-0.17.2 is the current version. Seems to work. I just re-built everything including the usrp code so I can build now. I'm still learning so many new things here that I'm not sure exactly which parts do which things. For example, if configure can set the install path to /usr/gr/local/lib it would seem make check would also be able to find libraries there. The path seems to show up in the Makefile but I need LD_LIBRARY_PATH to do make check. And I need to set TMPDIR for the usrp build even though /tmp and /var/tmp are available. Several other hacks to compile GnuRadio under FreeBSD but I'm getting there. Thanks for the help. -- LRK [EMAIL PROTECTED] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 07:31:52PM -0500, LRK wrote: > On Tue, Sep 20, 2005 at 10:21:57AM -0700, Eric Blossom wrote: > > > > > > Just to be sure things are right, I blew away the GnuRadio installed files > > > and re-built from CVS. Amazingly, one problem in the gnuradio-core build > > > seems to have disappeared but a new problem appeared in the audio-oss > > > build. > > > > A couple of basic comments: > > > > I assume that you know that the modules have to be built in a > > particular order to satisfy dependencies among themselves. > > The easiest way to handle this is to use: > > > > $ cd gr-build > > $ ./for-all-dirs ../buildit 2>&1 | tee make.log > > Yep, it does that. I run a script which does it the same way as before. > > > > > One more bug to hunt down to get back where I was: > > > > > Traceback (most recent call last): > > > File "./qa_oss.py", line 24, in ? > > > import audio_oss > > > File "/usr/gr/gr-build/gr-audio-oss/src/audio_oss.py", line 5, in ? > > > import _audio_oss > > > ImportError: /usr/gr/gr-build/gr-audio-oss/src/.libs/_audio_oss.so: > > > Undefined symbol "_ZN8gr_block5startEv" > > > FAIL: run_tests > > > > Did you "make install" gnuradio-core prior to trying to build audio_oss? > > (If you ../buildit in gnuradio-core, it would have done this for you.) > > Yep, the gnuradio-core was built, checked, and installed. Unlike the previous > CVS download, the gnuradio-core make check no longer fails. Not sure if that > is a clue. (I was having to do make install and then make check worked). > > > > It could be that you have an old installed version of the > > gnuradio-core library sitting in /usr/local/lib that is being > > referenced when running the gr-audio-oss tests. > > Indeed there was a /usr/local/lib/gnuradio-core.so.0, probably left from > some time ago when the 'prefix' got accidentally munged. I deleted that > and a link to it as well as looking around for any other pieces of GR there. > > So now the above error says it can't find gnuradio-core.so.0 which is in > fact installed in /usr/gr/local/lib. Looks like the ./configure sets the > '-L' variable to search that library. > > > I had set CPPFLAGS and LDFLAGS to add the /usr/local path to get the usrp > code to build but backing all that out doesn't recover. > > PYTHONPATH has not been changed. LD_LIBRARY_PATH has not been changed. > > Still looking All the modules that depend on gnuradio-core use pkg-config to locate the gnuradio-core library and includes at configure time. Which one it finds is dependent on the setting of the PKG_CONFIG_PATH environment variable. If you're installing gnuradio-core in /usr/gr/local, then you'll find that it installs a file: /usr/gr/local/lib/pkgconfig/gnuradio-core.pc The other gr-* packages need a way to find that file. They do that through the PKG_CONFIG_PATH environment variable. It wants to contain the path to that directory, and perhaps /usr/local/lib/pkgconfig too (or whereever fftw3f.pc was installed.) On one of my systems (x86 Mandrake 10.1 Official): $ echo $PKG_CONFIG_PATH /usr/local/lib/pkgconfig $ ls -l /usr/local/lib/pkgconfig/ total 48 -rw-rw-r-- 1 root root 220 Jan 21 2005 fftw3.pc -rw-rw-r-- 1 root root 221 Mar 7 2004 fftw3f.pc -rw-r--r-- 1 eb wheel 291 Sep 17 13:07 gnuradio-core.pc -rw-rw-r-- 1 root root 290 Jan 19 2004 jack.pc -rw-rw-r-- 1 root root 517 Jul 30 2004 libgeda.pc -rw-rw-r-- 1 root root 283 May 28 2003 libxine.pc -rw-rw-r-- 1 root root 250 Jan 20 2004 lrdf.pc -rw-rw-r-- 1 root root 256 Jan 20 2004 raptor.pc -rw-rw-r-- 1 root root 273 Jan 20 2004 samplerate.pc -rw-rw-r-- 1 root root 249 Jan 19 2004 sndfile.pc -rw-r--r-- 1 eb wheel 238 Aug 28 17:59 usrp.pc -rw-r--r-- 1 eb wheel 377 Jul 17 21:27 valgrind.pc On another (x86_64 SuSE 9.3 Professional): $ echo $PKG_CONFIG_PATH /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig $ ls -l /usr/local/lib64/pkgconfig total 8 -rw-r--r-- 1 eb eb 289 2005-08-28 18:50 gnuradio-core.pc -rw-r--r-- 1 eb eb 240 2005-09-20 01:20 usrp.pc $ ls -l /usr/lib64/pkgconfig total 292 -rw-r--r-- 1 root root 382 2005-06-10 18:43 alsa.pc -rw-r--r-- 1 root root 176 2005-03-23 09:45 art-sharp.pc -rw-r--r-- 1 root root 204 2005-03-19 12:35 audiofile.pc [... big snip ...] -r--r--r-- 1 root root 299 2005-03-22 09:25 xfixes.pc -r--r--r-- 1 root root 472 2005-03-22 09:25 xft.pc -r--r--r-- 1 root root 237 2005-03-22 09:25 xrender.pc $ ls -l /opt/gnome/lib64/pkgconfig total 372 -rw-r--r-- 1 root root 258 2005-03-22 09:57 atk.pc -rw-r--r-- 1 root root 382 2005-03-22 10:49 bonobo-activation-2.0.pc -rw-r--r-- 1 root root 331 2005-03-22 11:45 cspi-1.0.pc [... big snip ...] -rw-r--r-- 1 root root 280 2005-03-22 09:59 pangox.pc -rw-r--r-- 1 root root 174 2005-03-23 07:59 rhythmbox.pc -rw-r--r-- 1 root root 170 2005-03-23 09:57 xml2po.p
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 07:31:52PM -0500, LRK wrote: > > So now the above error says it can't find gnuradio-core.so.0 which is in > fact installed in /usr/gr/local/lib. Looks like the ./configure sets the > '-L' variable to search that library. > > > I had set CPPFLAGS and LDFLAGS to add the /usr/local path to get the usrp > code to build but backing all that out doesn't recover. > > PYTHONPATH has not been changed. LD_LIBRARY_PATH has not been changed. Well, that was not true. Make check needs LD_LIBRARY_PATH which was inadvertently munged while editing the environment variables. So this problem is now fixed. Back to compiling the usrp code again. -- LRK [EMAIL PROTECTED] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 10:21:57AM -0700, Eric Blossom wrote: > > > > Just to be sure things are right, I blew away the GnuRadio installed files > > and re-built from CVS. Amazingly, one problem in the gnuradio-core build > > seems to have disappeared but a new problem appeared in the audio-oss build. > > A couple of basic comments: > > I assume that you know that the modules have to be built in a > particular order to satisfy dependencies among themselves. > The easiest way to handle this is to use: > > $ cd gr-build > $ ./for-all-dirs ../buildit 2>&1 | tee make.log Yep, it does that. I run a script which does it the same way as before. > > One more bug to hunt down to get back where I was: > > > Traceback (most recent call last): > > File "./qa_oss.py", line 24, in ? > > import audio_oss > > File "/usr/gr/gr-build/gr-audio-oss/src/audio_oss.py", line 5, in ? > > import _audio_oss > > ImportError: /usr/gr/gr-build/gr-audio-oss/src/.libs/_audio_oss.so: > > Undefined symbol "_ZN8gr_block5startEv" > > FAIL: run_tests > > Did you "make install" gnuradio-core prior to trying to build audio_oss? > (If you ../buildit in gnuradio-core, it would have done this for you.) Yep, the gnuradio-core was built, checked, and installed. Unlike the previous CVS download, the gnuradio-core make check no longer fails. Not sure if that is a clue. (I was having to do make install and then make check worked). > It could be that you have an old installed version of the > gnuradio-core library sitting in /usr/local/lib that is being > referenced when running the gr-audio-oss tests. Indeed there was a /usr/local/lib/gnuradio-core.so.0, probably left from some time ago when the 'prefix' got accidentally munged. I deleted that and a link to it as well as looking around for any other pieces of GR there. So now the above error says it can't find gnuradio-core.so.0 which is in fact installed in /usr/gr/local/lib. Looks like the ./configure sets the '-L' variable to search that library. I had set CPPFLAGS and LDFLAGS to add the /usr/local path to get the usrp code to build but backing all that out doesn't recover. PYTHONPATH has not been changed. LD_LIBRARY_PATH has not been changed. Still looking -- LRK [EMAIL PROTECTED] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, 20 Sep 2005 21:48, Robert McGwier wrote: > Same here: > > Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not > compile. The latest version, 2_7_0 gets further into the build than > before but will not build. Since I could not figure out a single need > for it, I removed it from KD7LMO's baseline build stuff. Xerces is not required in order to run GNU Radio binaries. I'm not sure about the exact purpose of xcerses in connection with GNU Radio - documentation?. It is not missed here. > Please let me pass along a warning. A month ago, I upgraded gcc and > got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and > remake wxPython 2.6.1 in an abortive attempt to get beyond some of this > "coloring with Crayola crayon and finger painting" look with improperly > initialized controls/broken controls, etc. have in wxGtk/wxPython. > WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to > work since. I have been completely dead in the water, unable to > diagnose what was wrong other than import wx gave me "undefined symbols > in pango" even after I went backwards. I finally just pulled off my > personal files and rebuilt the distribution and used the wxGtk that came > with SUSE. I admit I had other things going on during that month that > interfered (the month from just north of the river Styx), but this was a > painful reminder of the old addage" if it ain't broke, don't fix it > unless you want to stall development. When upgrading a system this way, one has to ensure that all files of the old packages are getting uninstalled and all dependencies are updated as well. Mixing old and new binaries and libraries can cause havoc to the system. Using a good packaging system. that keeps track of package dependencies is the only safe way of upgrading packages. cheerio Berndt pgpZhUmsOLohz.pgp Description: PGP signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
Sure, I can remove the xerces stuff from the install. I think it may have been required for octave, but I'm not sure. If there are any other thoughts or suggestions, let me know. On Tue, 20 Sep 2005, Eric Blossom wrote: > On Tue, Sep 20, 2005 at 12:18:10PM +, Robert McGwier wrote: > > Same here: > > > > Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not > > compile. The latest version, 2_7_0 gets further into the build than > > before but will not build. Since I could not figure out a single need > > for it, I removed it from KD7LMO's baseline build stuff. > > > > Please let me pass along a warning. A month ago, I upgraded gcc and > > got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and > > remake wxPython 2.6.1 in an abortive attempt to get beyond some of this > > "coloring with Crayola crayon and finger painting" look with improperly > > initialized controls/broken controls, etc. have in wxGtk/wxPython. > > WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to > > work since. I have been completely dead in the water, unable to > > diagnose what was wrong other than import wx gave me "undefined symbols > > in pango" even after I went backwards. I finally just pulled off my > > personal files and rebuilt the distribution and used the wxGtk that came > > with SUSE. I admit I had other things going on during that month that > > interfered (the month from just north of the river Styx), but this was a > > painful reminder of the old addage" if it ain't broke, don't fix it > > unless you want to stall development. > > > > Bob > > Good points. > > KD7LMO, can you please remove xerces from your build instructions? > Not sure what program uses it, but it's not one of ours. > > Thanks, > Eric > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 10:39:33AM -0500, LRK wrote: > On Tue, Sep 20, 2005 at 12:18:10PM +, Robert McGwier wrote: > > I just built the usrp portion for the first time, not having a USRP I was > trying to learn more about the process by using the audio stuff. > I encountered several problems and posted questions to the list but got > no responses. After a bit more hacking, it appears usrp compiles Ok with > the FreeBSD port of libusb so maybe it will work. > > Just to be sure things are right, I blew away the GnuRadio installed files > and re-built from CVS. Amazingly, one problem in the gnuradio-core build > seems to have disappeared but a new problem appeared in the audio-oss build. A couple of basic comments: I assume that you know that the modules have to be built in a particular order to satisfy dependencies among themselves. The easiest way to handle this is to use: $ cd gr-build $ ./for-all-dirs ../buildit 2>&1 | tee make.log > One more bug to hunt down to get back where I was: > Traceback (most recent call last): > File "./qa_oss.py", line 24, in ? > import audio_oss > File "/usr/gr/gr-build/gr-audio-oss/src/audio_oss.py", line 5, in ? > import _audio_oss > ImportError: /usr/gr/gr-build/gr-audio-oss/src/.libs/_audio_oss.so: Undefined > symbol "_ZN8gr_block5startEv" > FAIL: run_tests Did you "make install" gnuradio-core prior to trying to build audio_oss? (If you ../buildit in gnuradio-core, it would have done this for you.) It could be that you have an old installed version of the gnuradio-core library sitting in /usr/local/lib that is being referenced when running the gr-audio-oss tests. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 12:18:10PM +, Robert McGwier wrote: > Same here: > > Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not > compile. The latest version, 2_7_0 gets further into the build than > before but will not build. Since I could not figure out a single need > for it, I removed it from KD7LMO's baseline build stuff. > > Please let me pass along a warning. A month ago, I upgraded gcc and > got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and > remake wxPython 2.6.1 in an abortive attempt to get beyond some of this > "coloring with Crayola crayon and finger painting" look with improperly > initialized controls/broken controls, etc. have in wxGtk/wxPython. > WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to > work since. I have been completely dead in the water, unable to > diagnose what was wrong other than import wx gave me "undefined symbols > in pango" even after I went backwards. I finally just pulled off my > personal files and rebuilt the distribution and used the wxGtk that came > with SUSE. I admit I had other things going on during that month that > interfered (the month from just north of the river Styx), but this was a > painful reminder of the old addage" if it ain't broke, don't fix it > unless you want to stall development. > > Bob Good points. KD7LMO, can you please remove xerces from your build instructions? Not sure what program uses it, but it's not one of ours. Thanks, Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
SUSE 9.3 is spectacularly solid with GnuRadio, has the low latency patches in the updated kernels, and YAST (Yet Another Somethingorother Tool) is really quite lovely as a system management tool. Upgrades are trivial.They distribute with a buggy version of gcc which they appear to have patched. What the patches consist of, I am too lazy and/or busy to find out. I downloaded and installed gcc 3.4.4 and have been very happy. Just do not try to upgrade Gtk until Eric and or others tell us that they have upgraded to (say) Gtk 2.8 and beyond and all of the funkiness with atk, pango, etc. have been worked out. I will really be happy to get an upgraded set of Gtk/Python tools at my disposal because the initialization of the controls (or lack thereof) is a pain. We should not have to touch controls to initialize them, or we should standardize on rc files where the "last setting" or a set of profiles is stored and read at user control. If I had time, I would do it. I do not have time. I need to use the USRP/GnuRadio for specific tasks and that consumes the time I have available for this. BTW, wxPython2.6.1 builds, installs, and works with the Gtk distributed with SUSE 9.3 SUSE 9.3 is why I have been stable on one distribution for months. Bob Alfred A. Aburto Jr. wrote: Otherwise, being brand new to LINUX, is SUSE (I have 9.2, not yet installe!) good? I have a new USRP (not out of the box yet) but I'm worried that I didn't go with Fedora Core 3 or 4... Thanks for feedback! Al > Robert McGwier wrote: ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 20, 2005 at 12:18:10PM +, Robert McGwier wrote: > > Please let me pass along a warning. A month ago, I upgraded gcc and > got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and > remake wxPython 2.6.1 in an abortive attempt to get beyond some of this > "coloring with Crayola crayon and finger painting" look with improperly > initialized controls/broken controls, etc. have in wxGtk/wxPython. > WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to > work since. I have been completely dead in the water, unable to > diagnose what was wrong other than import wx gave me "undefined symbols > in pango" even after I went backwards. I finally just pulled off my > personal files and rebuilt the distribution and used the wxGtk that came > with SUSE. I admit I had other things going on during that month that > interfered (the month from just north of the river Styx), but this was a > painful reminder of the old addage" if it ain't broke, don't fix it > unless you want to stall development. This seems to be a generic problem with GnuRadio. I notice a lot of newbies who show up here and ask for help but get no response. They seem to disappear never to be heard from again. I just built the usrp portion for the first time, not having a USRP I was trying to learn more about the process by using the audio stuff. I encountered several problems and posted questions to the list but got no responses. After a bit more hacking, it appears usrp compiles Ok with the FreeBSD port of libusb so maybe it will work. Just to be sure things are right, I blew away the GnuRadio installed files and re-built from CVS. Amazingly, one problem in the gnuradio-core build seems to have disappeared but a new problem appeared in the audio-oss build. One more bug to hunt down to get back where I was: gmake[2]: Leaving directory `/usr/gr/gr-build/gr-audio-oss' gmake[1]: Leaving directory `/usr/gr/gr-build/gr-audio-oss' Making check in config gmake[1]: Entering directory `/usr/gr/gr-build/gr-audio-oss/config' gmake[1]: Nothing to be done for `check'. gmake[1]: Leaving directory `/usr/gr/gr-build/gr-audio-oss/config' Making check in src gmake[1]: Entering directory `/usr/gr/gr-build/gr-audio-oss/src' gmake check-am gmake[2]: Entering directory `/usr/gr/gr-build/gr-audio-oss/src' gmake check-TESTS gmake[3]: Entering directory `/usr/gr/gr-build/gr-audio-oss/src' Traceback (most recent call last): File "./qa_oss.py", line 24, in ? import audio_oss File "/usr/gr/gr-build/gr-audio-oss/src/audio_oss.py", line 5, in ? import _audio_oss ImportError: /usr/gr/gr-build/gr-audio-oss/src/.libs/_audio_oss.so: Undefined symbol "_ZN8gr_block5startEv" FAIL: run_tests === 1 of 1 tests failed === gmake[3]: *** [check-TESTS] Error 1 gmake[3]: Leaving directory `/usr/gr/gr-build/gr-audio-oss/src' gmake[2]: *** [check-am] Error 2 gmake[2]: Leaving directory `/usr/gr/gr-build/gr-audio-oss/src' gmake[1]: *** [check] Error 2 gmake[1]: Leaving directory `/usr/gr/gr-build/gr-audio-oss/src' gmake: *** [check-recursive] Error 1 >>> build FAILED in /usr/gr/gr-build/gr-audio-oss -- LRK [EMAIL PROTECTED] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
Otherwise, being brand new to LINUX, is SUSE (I have 9.2, not yet installe!) good? I have a new USRP (not out of the box yet) but I'm worried that I didn't go with Fedora Core 3 or 4... Thanks for feedback! Al > Robert McGwier wrote: Same here: Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not compile. The latest version, 2_7_0 gets further into the build than before but will not build. Since I could not figure out a single need for it, I removed it from KD7LMO's baseline build stuff. Please let me pass along a warning. A month ago, I upgraded gcc and got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and remake wxPython 2.6.1 in an abortive attempt to get beyond some of this "coloring with Crayola crayon and finger painting" look with improperly initialized controls/broken controls, etc. have in wxGtk/wxPython. WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to work since. I have been completely dead in the water, unable to diagnose what was wrong other than import wx gave me "undefined symbols in pango" even after I went backwards. I finally just pulled off my personal files and rebuilt the distribution and used the wxGtk that came with SUSE. I admit I had other things going on during that month that interfered (the month from just north of the river Styx), but this was a painful reminder of the old addage" if it ain't broke, don't fix it unless you want to stall development. Bob Eric Blossom wrote: On Tue, Sep 13, 2005 at 07:12:30PM -0700, Tarif Hawasly wrote: Hi All I am new to Linux and new to gnu-radio. I followed the installation guidelines that are in http://www.kd7lmo.net/ground_gnuradio_install.html I am utilizing build_baseline.sh. when I install xerces-c-src_2_6_0 I do the following setenv XERCESCROOT $HOME/xerces-c-src_2_6_0 autoconf runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P $HOME/gr gmake after running gmake, gmake report [AbstractDOMParser.o] Error 1 [Parsers] Error 2 when I look at the result it report 1609 errors and they are all related to .cpp files I updated c++ and many other packages before running the baseline installation. So I do not know how to approach the problem Any help will be appreciated Tarif Hawasly If this was already answered, excuse my duplicate answer. xerces isn't required for GNU Radio, so not having it shouldn't be a problem. Don't know about your build problem. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
Same here: Under Suse 9.3 (WHICH I HAVE HAD FOR MONTHS) 8-) , xerces will not compile. The latest version, 2_7_0 gets further into the build than before but will not build. Since I could not figure out a single need for it, I removed it from KD7LMO's baseline build stuff. Please let me pass along a warning. A month ago, I upgraded gcc and got all bold (sigh). I attempted to upgrade pango, atk, gtk, wxgtk, and remake wxPython 2.6.1 in an abortive attempt to get beyond some of this "coloring with Crayola crayon and finger painting" look with improperly initialized controls/broken controls, etc. have in wxGtk/wxPython. WHAT A MISTAKE. I have been unable to go backwards and get gnuRadio to work since. I have been completely dead in the water, unable to diagnose what was wrong other than import wx gave me "undefined symbols in pango" even after I went backwards. I finally just pulled off my personal files and rebuilt the distribution and used the wxGtk that came with SUSE. I admit I had other things going on during that month that interfered (the month from just north of the river Styx), but this was a painful reminder of the old addage" if it ain't broke, don't fix it unless you want to stall development. Bob Eric Blossom wrote: On Tue, Sep 13, 2005 at 07:12:30PM -0700, Tarif Hawasly wrote: Hi All I am new to Linux and new to gnu-radio. I followed the installation guidelines that are in http://www.kd7lmo.net/ground_gnuradio_install.html I am utilizing build_baseline.sh. when I install xerces-c-src_2_6_0 I do the following setenv XERCESCROOT $HOME/xerces-c-src_2_6_0 autoconf runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P $HOME/gr gmake after running gmake, gmake report [AbstractDOMParser.o] Error 1 [Parsers] Error 2 when I look at the result it report 1609 errors and they are all related to .cpp files I updated c++ and many other packages before running the baseline installation. So I do not know how to approach the problem Any help will be appreciated Tarif Hawasly If this was already answered, excuse my duplicate answer. xerces isn't required for GNU Radio, so not having it shouldn't be a problem. Don't know about your build problem. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Instaling Baseline requirment problem
On Tue, Sep 13, 2005 at 07:12:30PM -0700, Tarif Hawasly wrote: > Hi All > > I am new to Linux and new to gnu-radio. I followed the > installation guidelines that are in > http://www.kd7lmo.net/ground_gnuradio_install.html > > I am utilizing build_baseline.sh. when I install > xerces-c-src_2_6_0 I do the following > > setenv XERCESCROOT $HOME/xerces-c-src_2_6_0 > autoconf > runConfigure -plinux -cgcc -xg++ -minmem -nsocket > -tnative -rpthread -P $HOME/gr > gmake > > after running gmake, gmake report > > [AbstractDOMParser.o] Error 1 > [Parsers] Error 2 > > when I look at the result it report 1609 errors and > they are all related to .cpp files > > I updated c++ and many other packages before running > the baseline installation. So I do not know how to > approach the problem > > Any help will be appreciated > > Tarif Hawasly If this was already answered, excuse my duplicate answer. xerces isn't required for GNU Radio, so not having it shouldn't be a problem. Don't know about your build problem. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
