[USRP-users] Custom filesystems for N310: adding gnuradio

Marcus Müller marcus.mueller at ettus.com
Sun Feb 10 04:38:57 EST 2019

Hi Ali,

the "pwd" in that path makes me suspicious. In the original
documentation (on github) this read `pwd` and would have been executed
to be replaced with the current working directory; sorry for the copy-
and-paste error on our side; on our documentation page, the `…`
converts to code formatting. So, the full command line would be

TEMPLATECONF=/home/oe-builder/meta-ettus/conf/sulfur source ./oe-
core/oe-init-build-env ./build ./bitbake

Best regards,

On Fri, 2019-02-08 at 14:19 -0800, Ali Dormiani via USRP-users wrote:
> Hello everyone,
> I've spent a few hours trying to learn docker and get a N310
> filesystem with gnuradio on it.
> So far no luck.
> I followed the documentation:
> https://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_fsbuild
> And got this output:
> WARNING: unable to chmod /home/oe-builder/build
> Error: TEMPLATECONF value points to nonexistent directory 'pwd/meta-
> ettus/conf/sulfur'
> Additionally, I have no idea how to compile gnuradio in the docker
> container. There are a lot of missing dependencies and there is no
> package manager. 
> Am I supposed to compile gnuradio's dependencies from source?
> Is it even reasonable to try to get gnuradio on a USRP SDIMG
> filesystem?
> I ask this last question because it seems strange the Ettus folks
> don't put gnuradio on the default filesystem. It's opensource, very
> useful, and there is plenty of free space (~7 Gb) in the stock
> partitions. Why not?
> Thank you all for your time,
> Ali
> _______________________________________________
> USRP-users mailing list
> USRP-users at lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

More information about the USRP-users mailing list