discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Problems building GNURadio


From: Michal Jakubiak
Subject: Re: [Discuss-gnuradio] Problems building GNURadio
Date: Mon, 22 Sep 2014 20:39:51 +0300

In my original post I was referring to this discussion: http://lists.gnu.org/archive/html/discuss-gnuradio/2014-08/msg00207.html
The output I've put in my first post already used these flags. That was for GR 3.7.5
I've used distcc to speed up the compilation, but it failed. I'm leaving the BBB for the night to compile 3.7.4 on it's own, just in case if distcc messed something up. If that doesn't work, I guess my next few questions will concern cross compiling and the contents of SDK ;)

BR,
Michal




On Mon, Sep 22, 2014 at 8:14 PM, Douglas Geiger <address@hidden> wrote:
Certainly you don't want to *disable* NEON when compiling for a platform that has it.

The SDK is designed for cross-compiling - I'll note that although the set of released SDK's are targetting Cortex-A9's, the emitted binaries will run on any ARMv7a chips (aside from the hf/sf ABI issues you need to understand).
If you're determined to native compile, then following the instructions under http://gnuradio.org/redmine/projects/gnuradio/wiki/Embedded#Native-Compiling should do the right thing. If that's not working for you, please do speak up.

I believe it came up during the Embedded WG discussion at GrCon last week that the wiki page has gotten to a good enough state that we probably do want to make it visible on the front page.

 Doug


On Mon, Sep 22, 2014 at 9:04 AM, Michal Jakubiak <address@hidden> wrote:
So disabling NEON is less than optimal solution. 

Thanks for the link: 
IMHO it deserves to be linked to the main gr wiki page.

I can't tell if it matters, but the SDK prepared for ARMv7hf is CortexA9 and BBB has CortexA8.
Also, if I understood correctly, the SDK is a package designed for cross-compiling. My OOT modules aren't big enough to be a problem for BBB to compile and as long as I can get Gnuradio working, I will be a very happy man. The closest I've ever gotten to cross-compiling was distcc and seeing the wiki page, I can tell that I need to read up on cross compiling and OE before I could make use of the information on the wiki.
I've naively compiled GR3.7.2 on BBB running Debian (I think it was 7.4) some time ago with surprisingly little problems (getting it to run on Raspberry Pi was a nightmare!).
Right now, I've downloaded GR7.4 and so far, 37% into compilation, there are no complaints from BBB.





On Sun, Sep 21, 2014 at 9:40 PM, Douglas Geiger <address@hidden> wrote:
I am curious to hear from folks if the changes made in this commit (https://github.com/gnuradio/gnuradio/commit/33a43b42c7ea3c318cbad3fe9372a32bc2bd127e) has any effect on cross-compiling. I verified it did the correct thing for me when using the SDK from the gnuradio wiki (i.e. the one linked to from http://gnuradio.org/redmine/projects/gnuradio/wiki/Embedded) targeting a Cortex-A9 machine, however I'd like to get feedback from other people using it. I am also not convinced that it is 'automagically' doing the right thing when native compiling still, but I don't have hardware in front of me to test that use case at the moment. In general I discourage native compiling something as large as GNURadio on smaller platforms unless there is no alternative (especially due to the memory requirements of building all the SWIG-related objects), but if there is a path to have cmake do the correct thing in all cases I think we want to do that.

 Doug



--
Doug Geiger
address@hidden


reply via email to

[Prev in Thread] Current Thread [Next in Thread]