[Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

Hello Michael! Thanks for your reply. Yes, indeed: I would have to "distclean" the build directory. But then, using cmake to re-build is kind of drifting away from the original pybombs problem. It is more or less reverting back to what I call "the good old way" (i.e. ./configure && make && make ins

Re: [Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

Hi Piotr - Yes, those are the correct lines to comment out. Remember that you'll need to "rm -rf" the build directory and start from scratch with the cmake command to get these changes to take ... cmake handles a lot of changes very robustly, but tweaks like this not so much so. I can't help with t

Re: [Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

Hello Michael, yes, this is true: # pacman -Ss libuhd community/libuhd 3.10.2.0-3 [installed] Universal Software Radio Peripheral (USRP) userspace driver So, apparently I had it installed. So, I did what you suggested (I think!): git diff host/CMakeLists.txt diff --git a/host/CMakeLists.txt

Re: [Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

Hi Piotr - The error you encountered generally means that UHD was already installed in the same prefix as the build would be going into, and that the UHD API changed between the versions. Normally UHD can be build over a pre-existing install, but sometime not too long ago this feature was broken vi

Re: [Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

Well, I came back to GR and app development based on GR after a long break. This is what I saw at https://wiki.gnuradio.org/index.php/ InstallingGRFromSource: *Using PyBOMBS* *We are moving to use PyBOMBS as our installation tool for GNU Radio. This will take care of dependencies and allow you to

[Discuss-gnuradio] build error at uhd::time_spec_t::get_system_time()

I am trying to build GR with PyBOMBS and apart from problems with the build system itself (it would not start properly when python3 is used) I get the following error not far away (85% complete) from the end of the build: [ 85%] Building CXX object gr-uhd/swig/CMakeFiles/_uhd_sw ig.dir/uhd_swigPYT

Re: [Discuss-gnuradio] build error

When you do git, you need to use the --recursive flag.

[Discuss-gnuradio] build error

hi there is an error in build of gnuradio the error is[ CMake Error at CMakeLists.txt:421 (message): VOLK required but not found. -- Configuring incomplete, errors occurred! ] suggest me solution for this thanks. ___ Discuss-gnuradio mailing list Di

[Discuss-gnuradio] Build error "/usr/local/lib/libpython2.7.a: error adding symbols: Bad value"

I have been attempting to build gnuradio from the source and have encountered this error which is obviously related to my Python installation. I have built Python2.7.8 from source with the confguration: ./configure --enable-shared --prefix=/usr/local I have read that without the --enable-shared

Re: [Discuss-gnuradio] build error

(please excuse the previous incomplete message) You will need to update the target_link_libraries section to add the following: ${Boost_FILESYSTEM_LIBRARY} This will link against the boost filesystem library and resolve the error you're receiving. - Marc On Sun, Mar 2, 2014 at 6:34 PM, Marc N

Re: [Discuss-gnuradio] build error

BZS, This error indicates that you aren't linking against the boost filesystem library. In the CMakeLists.txt file within the "lib" directory of the custom block, there will be a section that looks similar to this: target_link_libraries( ${GNURADIO_RUNTIME_LIBRARIES} ) This indicates that

[Discuss-gnuradio] build error

hi, when i install a new block ,try "make",i got these errors: CMakeFiles/test-scramble.dir/test_scramble.cc.o: In function `boost::filesystem::operator/(boost::filesystem::path const&, boost::filesystem::path const&)': test_scramble.cc:(.text._ZN5boost10filesystemdvERKNS0_4pathES3_[boost::filesy

Re: [Discuss-gnuradio] Build error

Hi Les, try to build with verbose output enabled, to see if there might be more errors/warnings. If I remember correctly you need to run something like this: make VERBOSE=1 If it does not work, search the list/website on how to turn verbose building on. Yours Martin PS: Please make sure yo

Re: [Discuss-gnuradio] Build error

I am into an area of which I have very little knowledge, but a lot of interest. Regards Les - Original Message - From: "Martin Lülf" To: Sent: Saturday, May 04, 2013 2:44 PM Subject: Re: [Discuss-gnuradio] Build error Am 04.05.2013 14:32, schrieb Les Barker: Hi All I turn t

Re: [Discuss-gnuradio] Build error

Am 04.05.2013 14:32, schrieb Les Barker: Hi All I turn to this discussion group in the hopes that someone can help! I am trying to build gnuradio on the way to achieving a working GQRX SDR program. I have tried various releases of gnuradio, including the latest, gnuradio-3.6.4.1, all with the sam

[Discuss-gnuradio] Build error

Hi All I turn to this discussion group in the hopes that someone can help! I am trying to build gnuradio on the way to achieving a working GQRX SDR program. I have tried various releases of gnuradio, including the latest, gnuradio-3.6.4.1, all with the same result i.e. [ 40%] Building CXX obje

Re: [Discuss-gnuradio] build error with "next" branch

On Thu, Feb 21, 2013 at 12:38 AM, Martin Braun (CEL) wrote: > Well, we do have crazy release cycles at the moment, and every new > release has *that* critical new feature. This also imposes theoretical > bounds on the quality of the documentation, because it's hard to keep > that up-to-date if th

Re: [Discuss-gnuradio] build error with "next" branch

20 February, 2013 18:19 > *To:* Ralph A. Schmid > *Cc:* discuss-gnuradio@gnu.org > > *Subject:* Re: [Discuss-gnuradio] build error with "next" branch > > ** ** > > On Wed, Feb 20, 2013 at 9:09 AM, Ralph A. Schmid wrote: > > > > > So much

Re: [Discuss-gnuradio] build error with "next" branch

enough. MB > > > > Ralph. > > > > From: Johnathan Corgan [mailto:johnat...@corganlabs.com] > Sent: Wednesday, 20 February, 2013 18:19 > To: Ralph A. Schmid > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] build error with "next" branch >

Re: [Discuss-gnuradio] build error with "next" branch

Well, this is exactly what everyone recommends _not_ to do, they tell, go with the latest sources. Ralph. From: Johnathan Corgan [mailto:johnat...@corganlabs.com] Sent: Wednesday, 20 February, 2013 18:19 To: Ralph A. Schmid Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio

Re: [Discuss-gnuradio] build error with "next" branch

and worked without manual changes. Ralph. From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom Rondeau Sent: Wednesday, 20 February, 2013 18:13 To: Ralph A. Schmid Cc: GNURadio Discussion List Subject: Re: [Discuss-gnuradio] build error with "next" branch

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 6:59 PM, Johnathan Corgan wrote: > On Wed, Feb 20, 2013 at 9:23 AM, Marcus D. Leech wrote: > >> >> How up-to-date are the Ubuntu packages? > > Release 3.6.1. If the timing works out, it looks like we can still get > 3.6.3 or 3.6.4 (not yet released) into 13.04. > I'm won

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 12:41 PM, Alexandru Csete wrote: > I'm wondering what makes you think that given that the current version > in 13.04 alpha is still 3.6.1? > Release 3.6.3 has already been packaged for Debian; it's only a matter of coordination to see if it can get into Ubuntu. > I do

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 9:19 AM, Ralph A. Schmid wrote: > ** > > OK, below the output. > > > > "Master" runs just fine through the whole process and runs, so I assume > the system should be OK so far. The only non standard stuff on the system > is a minimum gnuradio 3.4.2 installation for OpenBTS

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 12:09 PM, Ralph A. Schmid wrote: > ** > > The build and build install worked just fine, but now the crazy thing > complains that the pythonpath is not set. Huh?! Why does a new build > influence a environment variable? And I have no idea how to handle these > things under

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 9:23 AM, Marcus D. Leech wrote: > How up-to-date are the Ubuntu packages? > Release 3.6.1. If the timing works out, it looks like we can still get 3.6.3 or 3.6.4 (not yet released) into 13.04. Johnathan ___ Discuss-gnuradio m

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 12:23 PM, Marcus D. Leech wrote: > ** > > On Wed, Feb 20, 2013 at 9:09 AM, Ralph A. Schmid wrote: > > >> So much to learn that I never wanted to know :) >> > > It is for this reason that I will be happy when the majority of users > install GNU Radio via operating system

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 9:09 AM, Ralph A. Schmid > wrote: So much to learn that I never wanted to know :) It is for this reason that I will be happy when the majority of users install GNU Radio via operating system vendor supplied packages. Right now this can be

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 9:09 AM, Ralph A. Schmid wrote: > So much to learn that I never wanted to know :) > It is for this reason that I will be happy when the majority of users install GNU Radio via operating system vendor supplied packages. Right now this can be done using Ubuntu 12.10, Debi

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 12:09 PM, Ralph A. Schmid > wrote: __ The build and build install worked just fine, but now the crazy thing complains that the pythonpath is not set. Huh?! Why does a new build influence a environment variable? And I have no idea h

Re: [Discuss-gnuradio] build error with "next" branch

The build and build install worked just fine, but now the crazy thing complains that the pythonpath is not set. Huh?! Why does a new build influence a environment variable? And I have no idea how to handle these things under Linux :-( So much to learn that I never wanted to know :) Ralph.

Re: [Discuss-gnuradio] build error with "next" branch

The build and build install worked just fine, but now the crazy thing complains that the pythonpath is not set. Huh?! Why does a new build influence a environment variable? And I have no idea how to handle these things under Linux :-( So much to learn that I never wanted to know :) Ralph.__

Re: [Discuss-gnuradio] build error with "next" branch

1.6 GHz compiling takes a while... Ralph. From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom Rondeau Sent: Wednesday, February 20, 2013 4:31 PM To: Ralph A. Schmid, dk5ras Cc: GNURadio Discussion List Subject: Re: [Discuss-gnuradio] build error with "next&qu

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 7:30 AM, Tom Rondeau wrote: > On Wed, Feb 20, 2013 at 9:49 AM, Ralph A. Schmid, dk5ras > wrote: > > Actually, yes, delete the build directory. There's possibly some stuff > that's built there that's confusing things. Cmake should automatically tell > that things are old a

Re: [Discuss-gnuradio] build error with "next" branch

ondeau > *Sent:* Wednesday, February 20, 2013 3:25 PM > *To:* Ralph A. Schmid > *Cc:* GNURadio Discussion List > *Subject:* Re: [Discuss-gnuradio] build error with "next" branch > > ** ** > > On Wed, Feb 20, 2013 at 9:19 AM, Ralph A. Schmid wrote: > > &g

Re: [Discuss-gnuradio] build error with "next" branch

ndeau Sent: Wednesday, February 20, 2013 3:25 PM To: Ralph A. Schmid Cc: GNURadio Discussion List Subject: Re: [Discuss-gnuradio] build error with "next" branch On Wed, Feb 20, 2013 at 9:19 AM, Ralph A. Schmid wrote: OK, below the output. "Master" runs just fine through th

Re: [Discuss-gnuradio] build error with "next" branch

OK, below the output. "Master" runs just fine through the whole process and runs, so I assume the system should be OK so far. The only non standard stuff on the system is a minimum gnuradio 3.4.2 installation for OpenBTS, some command line tools that somehow depend on UHD and RTLSDR and maybe g

Re: [Discuss-gnuradio] build error with "next" branch

On Wed, Feb 20, 2013 at 7:54 AM, Ralph A. Schmid, dk5ras wrote: > Hi, > > Kubuntu 12.04 32bit LTS, latest gnuradio "master", everything works. Now I > thought, give "next" a try, but this fails. Before I go into details and > search for the exact error, I followed this procedure mentioned below. I

[Discuss-gnuradio] build error with "next" branch

Hi, Kubuntu 12.04 32bit LTS, latest gnuradio "master", everything works. Now I thought, give "next" a try, but this fails. Before I go into details and search for the exact error, I followed this procedure mentioned below. Is this the correct way, or is this already part of the problem? :) "git c

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

I have been able to work on this tonight, and I think the solution is that we just needed to be more specific in our LDADDs in a few places. Mostly, it's where we are building programs (noinst_PROGRAMS = ), but we were only passing an LDADD of a few libraries and not everything. I was wondering

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On Thu, Mar 31, 2011 at 2:44 PM, Marcus D. Leech wrote: > On 03/31/2011 01:36 PM, Nick Foster wrote: > >> On Wed, 2011-03-30 at 20:44 -0400, Marcus D. Leech wrote: >> That's it, all right. volk_common.h defines a union which includes >> __m128i, which is only defined in SSE2 (emmintrin.h) and hig

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On 03/31/2011 01:36 PM, Nick Foster wrote: On Wed, 2011-03-30 at 20:44 -0400, Marcus D. Leech wrote: That's it, all right. volk_common.h defines a union which includes __m128i, which is only defined in SSE2 (emmintrin.h) and higher -- but the test Volk uses for this union is only (if LV_HAS_MMX).

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On Wed, 2011-03-30 at 20:44 -0400, Marcus D. Leech wrote: > On 03/30/2011 07:33 PM, Tom Rondeau wrote: > > On Wed, Mar 30, 2011 at 6:17 PM, Marcus D. Leech > > wrote: > > Get the following build error from very-recent GIT sources, > > on Ubuntu 10.04, on x86 machine: > >

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On 31-03-11 16:40, Johnathan Corgan wrote: On Thu, Mar 31, 2011 at 06:09, Sim IJskes wrote: This problem should be solved when you have applied the patch i posted in: Thanks for your patch; it shows how to correct the problem in one area. Tom and I are trying to work out how to solve this i

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Thu, Mar 31, 2011 at 06:01, azim...@gmail.com wrote: > Four more errors of the same type (no rule to make xyz). The work > arounds are obviously not the solution, but I have no time to look > into this more deeply: This sounds like something different from the DSO linking issue. Johnathan _

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Thu, Mar 31, 2011 at 06:09, Sim IJskes wrote: > This problem should be solved when you have applied the patch i posted in: Thanks for your patch; it shows how to correct the problem in one area. Tom and I are trying to work out how to solve this in a more general way so it doesn't require as

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On 31-03-11 11:54, azim...@gmail.com wrote: Thanks guys. Here's the latest update on errors and solutions: gr-usrp/apps needs: ../../gnuradio-core/src/lib/.libs/libgnuradio-core-3.4.0git.so.0 ../../usrp/host/lib/.libs/libusrp-3.4.0git.so.0 (twice: both for usrp_rx_cfile and for usrp_siggen)

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

Four more errors of the same type (no rule to make xyz). The work arounds are obviously not the solution, but I have no time to look into this more deeply: gr-gsm-fr-vocoder/src/lib needs: ln -s {python/,}gsm_full_rate.cc gr-noaa/swig needs: ln -s {python/,}noaa_swig.cc gr-trellis/src/lib needs:

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

Correction: Distro GCC binutils Ubuntu 10.044.4 2.20 Ubuntu 10.104.4 2.20 Ubuntu 11.044.5 2.21 Fedora 15 4.6 2.21 What I'm saying is, 10.04 == 10.10, so you shouldn't see much difference (only boost went from 1.40 to 1.42), but you should see

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

PS Distro GCC binutils Ubuntu 10.044.4 2.21 Ubuntu 10.104.4 2.20 Ubuntu 11.044.5 2.21 Fedora 15 4.6 2.21 Dimitrios Symeonidis "If you think you're too small to make a difference, try sleeping with a mosquito!" - Amnesty International On 3

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On 31-03-11 11:54, azim...@gmail.com wrote: Thanks guys. Here's the latest update on errors and solutions: == gruel/src/lib needs: -lboost_system -lboost_filesystem gr-usrp/apps needs: ../../gnuradio-core/src/lib/.libs/libgnuradio-core-3.4.0git.so.0 ../../usrp/host/lib/

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

Thanks guys. Here's the latest update on errors and solutions: == gruel/src/lib needs: -lboost_system -lboost_filesystem gr-usrp/apps needs: ../../gnuradio-core/src/lib/.libs/libgnuradio-core-3.4.0git.so.0 ../../usrp/host/lib/.libs/libusrp-3.4.0git.so.0 (twice: both for u

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On 03/30/2011 07:33 PM, Tom Rondeau wrote: On Wed, Mar 30, 2011 at 6:17 PM, Marcus D. Leech > wrote: Get the following build error from very-recent GIT sources, on Ubuntu 10.04, on x86 machine: libtool: compile:gcc -DHAVE_CONFIG_H -I. -I.. -I../include

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On 03/30/2011 07:33 PM, Tom Rondeau wrote: On Wed, Mar 30, 2011 at 6:17 PM, Marcus D. Leech > wrote: Get the following build error from very-recent GIT sources, on Ubuntu 10.04, on x86 machine: libtool: compile:gcc -DHAVE_CONFIG_H -I. -I.. -I../include

Re: [Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

On Wed, Mar 30, 2011 at 6:17 PM, Marcus D. Leech wrote: > Get the following build error from very-recent GIT sources, on Ubuntu > 10.04, on x86 machine: > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../lib > -I/usr/include -I../include -m32 -m3dnow -mmmx -msse -g -O2 -MT vol

[Discuss-gnuradio] Build error on Ubuntu 10.04 on x86

Get the following build error from very-recent GIT sources, on Ubuntu 10.04, on x86 machine: libtool: compile:gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../lib -I/usr/include -I../include -m32 -m3dnow -mmmx -msse -g -O2 -MT volk.lo -MD -MP -MF .deps/volk.Tpo -c volk.c-fPIC -DPIC -o .libs/vol

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Wed, Mar 30, 2011 at 6:07 PM, Tom Rondeau wrote: > On Wed, Mar 30, 2011 at 11:59 AM, Johnathan Corgan > wrote: >> >> On Wed, Mar 30, 2011 at 08:18, azim...@gmail.com >> wrote: >> >> > Hi all, does anyone else get this error message when compiling >> > GnuRadio? This is with latest code from t

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Wed, Mar 30, 2011 at 11:59 AM, Johnathan Corgan < jcor...@corganenterprises.com> wrote: > On Wed, Mar 30, 2011 at 08:18, azim...@gmail.com > wrote: > > > Hi all, does anyone else get this error message when compiling > > GnuRadio? This is with latest code from today's master git tree, on > > U

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Wed, Mar 30, 2011 at 11:18 AM, azim...@gmail.com wrote: > Hi all, does anyone else get this error message when compiling > GnuRadio? This is with latest code from today's master git tree, on > Ubuntu 11.04, boost 1.42 > Oh come on! It's still March, what are you doing on 11.04? So this is t

Re: [Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

On Wed, Mar 30, 2011 at 08:18, azim...@gmail.com wrote: > Hi all, does anyone else get this error message when compiling > GnuRadio? This is with latest code from today's master git tree, on > Ubuntu 11.04, boost 1.42 > > I can bypass this by manually adding -lboost_system -lboost_filesystem Thi

[Discuss-gnuradio] build error: test_gruel.o: undefined reference to symbol 'boost::system::get_system_category()'

Hi all, does anyone else get this error message when compiling GnuRadio? This is with latest code from today's master git tree, on Ubuntu 11.04, boost 1.42 I can bypass this by manually adding -lboost_system -lboost_filesystem make[7]: Entering directory `/home/azimout/gnuradio/gruel/src/lib'

Re: [Discuss-gnuradio] Build error GNU Radio release v3.3.1git-971-ga02bb131

On Sun, Feb 27, 2011 at 6:51 AM, Arya Santini wrote: > Hi Jared, thanks for that suggestion. > > Anyway, I realized that I was using GNU compiler gcc-4.6 > (experimental) which apparently imposes stricter rules and allows > package builds to fail where previous versions used to succeed. So the > s

Re: [Discuss-gnuradio] Build error GNU Radio release v3.3.1git-971-ga02bb131

Hi Jared, thanks for that suggestion. Anyway, I realized that I was using GNU compiler gcc-4.6 (experimental) which apparently imposes stricter rules and allows package builds to fail where previous versions used to succeed. So the suggested fix for one typical "ptrdiff_t does not name a type" is

Re: [Discuss-gnuradio] Build error GNU Radio release v3.3.1git-971-ga02bb131

Hello Arya, AS> I was trying to build the gnuradio on yet AS> another machine running Ubuntu 10.10. from AS> source today after checking out the latest AS> code from the dev trunk: I see Ubuntu 10.10 has native packages. Is there a reason why you need to compile it? Perhaps you are l

[Discuss-gnuradio] Build error GNU Radio release v3.3.1git-971-ga02bb131

Hi List, I was trying to build the gnuradio on yet another machine running Ubuntu 10.10. from source today after checking out the latest code from the dev trunk: git clone http://gnuradio.org/git/gnuradio.git Then I set the branch to next, so that I can build gr-uhd as well. (Prior to this I'd s

回复： [Discuss-gnuradio] build error when ma king gnuradio 3.2 on Angstrom/OE

o] Error 1 - Is there any approaches to fix it? Thanks a lot! Zhen 发件人： Philip Balister 收件人： Zhen 发送日期： 2010/11/3 (周三) 5:44:09 下午 主 题： Re: [Discuss-gnuradio] build error when making gnuradio 3.2 on Angstrom/OE On 11/03/2010 05:04 PM, Zhen wrote:

Re： [Discuss-gnuradio] build error when maki ng gnuradio 3.2 on Angstrom/OE

o] Error 1 - Is there any approaches to fix it? Thanks a lot! Zhen 发件人： Philip Balister 收件人： Zhen 发送日期： 2010/11/3 (周三) 5:44:09 下午 主 题： Re: [Discuss-gnuradio] build error when making gnuradio 3.2 on Angstrom/OE On 11/03/2010 05:04 PM, Zhen wrote:

[Discuss-gnuradio] build error when making gnuradio 3.2 on Angstrom/OE

Hi, All, Now I am trying to install GNU Radio 3.2 on Angstrom and Beagleboard, following Philip's instruction on http://www.opensdr.com/node/17 'Configure' succeed, but 'make' failed just at the beginning with the following errors. --

Re: [Discuss-gnuradio] build error

Da! thanks Achilleas On Sun, Oct 24, 2010 at 11:54 AM, Tom Rondeau wrote: > On Sun, Oct 24, 2010 at 11:35 AM, Achilleas Anastasopoulos > wrote: >> yes, i can run all the tests in the different example directories. >> >> However i cannot find/run  grc >> >> Achilleas > > > "grc"

Re: [Discuss-gnuradio] build error

On Sun, 2010-10-24 at 11:35 -0400, Achilleas Anastasopoulos wrote: > yes, i can run all the tests in the different example directories. > > However i cannot find/run grc > > Achilleas > GRC is now called gnuradio-companion due to a naming conflict with an existing program. --n > On Sun, Oct

Re: [Discuss-gnuradio] build error

On Sun, Oct 24, 2010 at 11:35 AM, Achilleas Anastasopoulos wrote: > yes, i can run all the tests in the different example directories. > > However i cannot find/run  grc > > Achilleas "grc" was changed a bit back to "gnuradio-companion" because of a naming conflict. Is that available? Tom >

Re: [Discuss-gnuradio] build error

yes, i can run all the tests in the different example directories. However i cannot find/run grc Achilleas On Sun, Oct 24, 2010 at 11:08 AM, Tom Rondeau wrote: > On Sun, Oct 24, 2010 at 10:48 AM, Achilleas Anastasopoulos > wrote: >> I am trying a new build from the source tree on fedora 12. >

Re: [Discuss-gnuradio] build error

On Sun, Oct 24, 2010 at 10:48 AM, Achilleas Anastasopoulos wrote: > I am trying a new build from the source tree on fedora 12. > Configure gives the result shown at the end of the email. > Make and make check complete fine, but sudo make install > completes with the message: > *** Post-Install Mes

[Discuss-gnuradio] build error

I am trying a new build from the source tree on fedora 12. Configure gives the result shown at the end of the email. Make and make check complete fine, but sudo make install completes with the message: *** Post-Install Message *** Warning: python could not find the gnuradio module. Make su

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Hi Alex - Good to hear you're up and running with GR on OSX. And, you're welcome. - MLD On May 25, 2009, at 5:53 PM, Alexander List wrote: OK, tried again using a fresh gr 3.2 checkout, worked without errors. All passed fine as they should. The compulsory test (listening to a local FM radio s

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

'doh... Forgot to reinstall swig after my Macbook reinstall. Did that, removed the files as suggested, svn up, bootstrap etc. and it built fine... added script to my MacPorts package install script so I don't forget it next time... Now I'm running into some Python library version conflicts when t

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Hi Alex - On May 24, 2009, at 4:24 PM, Alexander List wrote: make[5]: *** No rule to make target `gnuradio_swig_py_runtime.h', needed by `all'. Stop. The rule is located in gnuradio-core/src/lib/swig/Makefile.swig.gen , which is included in that directory's Makefile.am directly; maybe t

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Alexander List wrote: Is anyone else using OS X and succeeds to build gnuradio 3.2 without issues? A little while ago, I built 3.2 RC2 on a Macbook Pro running 10.4.11 and didn't encounter any problems (other than Macports installing all sorts of extra stuff if you don't set the swig instal

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

On May 24, 2009, at 4:24 PM, Alexander List wrote: Is anyone else using OS X and succeeds to build gnuradio 3.2 without issues? I've installed GNU Radio many times, latest being trunk revision 11081 (21 May 2009). I haven't tried since then; I'll be checking out the 3.2 release tomorrow.

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Alexander List wrote: > Michael Dickens wrote: > >> Hi Alex - In the file 'gnuradio-core/src/lib/Makefile.am', remove the >> entry "missing/libmissing.la" from the entry for >> "libgnuradio_core_qa_la_LIBADD". Here's the "svn diff". Let me / the >> list know if this works. - MLD >> > Yep,

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Michael Dickens wrote: > Hi Alex - In the file 'gnuradio-core/src/lib/Makefile.am', remove the > entry "missing/libmissing.la" from the entry for > "libgnuradio_core_qa_la_LIBADD". Here's the "svn diff". Let me / the > list know if this works. - MLD Yep, that worked, thanks. But now I get another

Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Hi Alex - In the file 'gnuradio-core/src/lib/Makefile.am', remove the entry "missing/libmissing.la" from the entry for "libgnuradio_core_qa_la_LIBADD". Here's the "svn diff". Let me / the list know if this works. - MLD === --

[Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign

Hi, trying to build gnuradio on OS X 10.4, I get ---8<--- Extracting /Users/alex/Documents/work/nc-projects/gr/gnuradio/gnuradio-core/src/lib/missing/.libs/libmissing.a (cd .libs/libgnuradio-core-qa.lax/libmissing.a && ar x /Users/alex/Documents/work/nc-projects/gr/gnuradio/gnuradio-core/src/lib

[Discuss-gnuradio] Build Error on SVN Trunk

Latest SVN trunk checked out this morning ... a clean checkout and build, on OSX 10.5 / XCode 3.0 (gcc 4.0.1) / MacPorts latest, results in the error: ../../../gr-msdd6000/src/msdd6000.h:6:26: error: linux/socket.h: No such file or directory So, either this module needs to be disabled for

Re: [Discuss-gnuradio] Build error under OS X

On Thu, Jan 17, 2008 at 12:29:15PM -0800, David Burgess wrote: > All - > > I just tried to build the trunk gnuradio from SVN under OS X 10.4.11 with > > ./configure --disable-all-components --enable-usrp --enable-omnithread > --enable-mblock --enable-pmt > make -j 2 > > > It ended thus: > > ... >

Re: [Discuss-gnuradio] Build error under OS X

According to < http://www.gnuradio.org/trac/browser/gnuradio/trunk/ README > , (10), you need guile 1.6 or 1.8 . Try upgrading to either of those, and if that doesn't fix the problem then we'll try something else. - MLD ___ Discuss-gnuradio maili

[Discuss-gnuradio] Build error under OS X

All - I just tried to build the trunk gnuradio from SVN under OS X 10.4.11 with ./configure --disable-all-components --enable-usrp --enable- omnithread --enable-mblock --enable-pmt make -j 2 It ended thus: ... GUILE_LOAD_PATH="/Users/dburgess/RangeNetworks/rangeNetworks/openBTS2/ packag

Re: [Discuss-gnuradio] build error in cygwin

Don, it worked with the minor modification that PYTHON PATH should be set appropriately before step (13). Here is the patch for the wiki: (11) Build wxPython: cd $WXDIR/wxPython python setup.py build_ext --inplace WXPORT=msw BUILD_GLCANVAS=0 BUILD_GIZMOS=0 UNICODE=0 This builds the Python co

Re: [Discuss-gnuradio] build error in cygwin

"Achilleas Anastasopoulos" <[EMAIL PROTECTED]> wrote: I followeed the wiki instructions for building gnuradio on cygwin. Everything seems to be working fine, except when installing wxPython. In particular in step (11) as described in the wiki: > cd $WXDIR/wxPython > python setup.py build_ext --

[Discuss-gnuradio] build error in cygwin

Hi, I followeed the wiki instructions for building gnuradio on cygwin. Everything seems to be working fine, except when installing wxPython. In particular in step (11) as described in the wiki: > cd $WXDIR/wxPython > python setup.py build_ext --inplace WXPORT=msw BUILD_GLCANVAS=0 BUILD_GIZMOS=0

Re: [Discuss-gnuradio] build error: test fails in gr_vmcircbuf_mmap_shm_open_factory

Eric Blossom wrote: Testing gr_vmcircbuf_mmap_shm_open_factory... /bin/sh: line 1: 29405 Aborted ${dir}$tst FAIL: test_all === 1 of 1 tests failed === Hi Patrick, We've seen this problem or something very similar to it in the past. Mostly we've

Re: [Discuss-gnuradio] build error: test fails in gr_vmcircbuf_mmap_shm_open_factory

On Sun, Jun 19, 2005 at 09:18:34PM +0200, Patrick Strasser wrote: > Hello! > > My build processed > > [EMAIL PROTECTED]:~/src/gnuradio-cvs/gr-build$ ./for-all-dirs ../buildit > 2>&1 | tee make.log > > stopped with this error (tee make.log helped a lot :-)): > > .Testing gr_vmcircbuf_sysv_shm_f

[Discuss-gnuradio] build error: test fails in gr_vmcircbuf_mmap_shm_open_factory

Hello! My build processed [EMAIL PROTECTED]:~/src/gnuradio-cvs/gr-build$ ./for-all-dirs ../buildit 2>&1 | tee make.log stopped with this error (tee make.log helped a lot :-)): make[2]: Leaving directory `/home/past/src/gnuradio-cvs/gr-build/gnuradio-core/src/lib' Making check in tests make