Re: [Discuss-gnuradio] Building on ODroid C2 running CentOS 7 report.

[Lamar Owen]

Marcus,

Thanks for the information.

Once EPEL is available for AArch64, it won't be hard at all, as there is 
already a GNURadio 3.7.5 package with SPEC and such, and at that point 
it won't be difficult to do.  I sent a separate message about that, 
though.....

But at the moment EPEL is not available for AArch64, and so I am 
building the dependencies from the EPEL source RPM's (rpmbuild and I, 
from before rpmbuild was split out of the main rpm executable, are old 
friends.....).  EPEL for AArch64 is likely being held up for RHEL for 
ARM64, which might possibly happen with the RHEL 7.3 release (but might 
not, too.....).  The CentOS developers are doing an ARMv7 (armv7hfp) but 
not an ARMv8 (aarch64).  So I'm incrementally building and installing 
select RPMs from EPEL now for aarch64, and I'll have all that for each 
build.

Cross-building of RPM's would be an interesting skill to learn, and 
maybe I'll go down that path at some point (point mock to the 
appropriate executables for the compilers and it should work, but might 
not......) but RPM buildhosts typically are native or emulated (QEMU 
buildhosts for some architectures are possible).

Oddly, my time is easier to justify than electricity here..... but then 
again, I'm the CIO here......

On 04/28/2016 01:48 PM, Marcus Müller wrote:
> I can really well understand the nature of "wanting to learn by doing"
> :) but since GNU Radio builds excellently without GRC or graphical
> (gr-qtgui, gr-wxgui, gr-sdl) interfaces, I'd really say: Start with GNU
> Radio minus graphical stuff – adding that later on when necessity
> dictates is probably a good idea, but for now, it sounds a bit
> "overkilly", to be honest.
>
> If you want to wrap things up for multiple different deployments (or
> even just deployments at different times), going the extra mile of
> cross-building a CentOS package definitely sounds like the skill I'd
> prefer to have, rather than building on the device itself.
> That way, installing GR boils down to a simple rpm command, rather than
> a recompile just to get this stuff done on yet another machine. Also, if
> there's already a gnuradio package SPEC that defines all the
> dependencies, rpmbuild will take care of making sure everything
> necessary to do the package build will be there – no manual chasing
> dependency rabbits down dependency holes, and the resulting binary
> package will automatically demand that you yum install the GNU Radio
> dependencies. Notice that if your .edu, the electricity spent on
> cross-compilation is probably paid for, whereas your hours chasing
> dependencies might or might not be :D