This is perfect. Thank you!

On Fri, Jan 24, 2020 at 4:22 PM Vasil Velichkov <vvvelich...@gmail.com>
wrote:

> Hi Andrew,
>
> Take a look at centos-7.6.Dockerfile[1] that is used by the gnuradio's
> buildbots[2]. Builds from the master branch currently fail because of some
> recently merged changes but I just tested build of maint-3.8 branch
> successfully.
>
> Most of the dependencies are installed from the CentOS and EPEL[3]
> repositories but some are installed by rebuilding source RPMs, from source
> release tarballs or using pip3. The python version is 3.6 and is installed
> from the base CentOS repository (python36-devel package)
>
> [1]
> https://github.com/gnuradio/gnuradio-buildbot/blob/public/worker/centos-7.6.Dockerfile
> [2] https://ci.gnuradio.org/buildbot/#/builders/59
> [3] https://fedoraproject.org/wiki/EPEL
>
> Regards,
> Vasil
>
> On 21/01/2020 05.15, Andrew J Wolfram wrote:
> > Hi All,
> >
> > Has anyone out there been able to install GNU Radio 3.8 on Centos 7? I
> have
> > gotten close compiling from source, but ultimately ran into a
> segmentation
> > fault when running gnuradio-companion.  The gdb output was not really
> > helpful. Frame 1 said "Cannot access memory at address 0x170e70>) at
> > /usr/include/string.h". I'm guessing something is wonky with the library
> > linking due to the piecemeal dependency resolution I had to do. When
> > running the cmake command I get a few "Cannot generate a safe runtime
> > search path for target because files in some directories may conflict
> with
> > libraries in implicit directories" errors. Perhaps that's related. I've
> had
> > a very difficult time installing dependencies since some of the most
> recent
> > versions are not available via yum. I've had luck using Anaconda (conda),
> > but that's contributed to the linking issues since the old version is
> > installed somewhere in /usr/ and the newest version is under the Anaconda
> > prefix.
> >
> > I got absolutely nowhere with pybombs.
> >
> > Is this a doomed endeavor?
> >
> > Thanks,
> > Andrew
> >
>
>

Reply via email to