discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] [PyBOMBS] pre-2.1.0 release testing on CentOS 7


From: Martin Braun
Subject: Re: [Discuss-gnuradio] [PyBOMBS] pre-2.1.0 release testing on CentOS 7
Date: Fri, 3 Jun 2016 10:27:01 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

Eric, and all other CentOS users,

I really want PyBOMBS to be able to install GNU Radio etc. with a single
command, but it doesn't always have to be the same one. The distro
that's seemingly causing the most trouble is CentOS, so if we need to
adapt the recipe specifically for CentOS to save us tons of work, why not.

If another recipe, e.g. gnuradio-default-centos, would help building for
CentOS users, let's just add that instead of trying to catch all these
issues.

However, if this is stuff that also affects other users, such as Ubuntu
14.04 users, we'll need to figure this out. Again, I appreciate lots of
feedback from people out there.

I have 2 14.04 machines which both seem to work, but they don't always
behave the same. It's probably a function of what else is installed, but
there's just too many parameters to fully understand.

Cheers,
M

On 06/03/2016 09:46 AM, Eric Statzer wrote:
> Hmm, nope thrift is not building successfully.  I guess the failure was
> masked since thrift is an "optional" package.  I get the error:
> 
>         ./configure: line 17775: syntax error near unexpected token `QT,'
>         ./configure: line 17775: `    PKG_CHECK_MODULES(QT, QtCore >=
> 4.3, QtNetwork >= 4.3, have_qt=yes, have_qt=no)'
> 
> which is actually an issue with the version of pkg-config on CentOS 7:
>         $ pkg-config --version
>         0.27.1
> 
> Everyone should get a kick out of this: I had fixed this once before [1]
> but it was actually YOU, Marcus, that broke it again! [2]
> 
> I'll revisit the pkg-config version issue again.  I think it was just
> the libtool version of commit 489762b that was causing heartburn (with
> Ubuntu 14.04, if I recall).  I agree that the version requirement of
> libtool was probably over-specced, but it looks like we still need
> pkg-config >= 2.8.
> 
> A change like this will probably require regression testing on the major
> distros, do we want to wade in to the dangerous waters of identifying
> what those distros are?  I guess I'm willing to set up docker images
> (like [3], which I need to update to install as a non-root user) to test
> Ubuntu 16.04/14.04 and CentOS 7.  If there are other distros we want to
> hit we might need another volunteer.
> 
> -Eric
> 
> [1]
> https://github.com/gnuradio/gr-recipes/commit/489762b65a6c457b9331984355f260e299c5e983
> [2]
> https://github.com/gnuradio/gr-recipes/commit/0913e49b630fcc93859610e40c36aaf29f4795dc
> [3] https://github.com/estatz/docker_centos7_gr
> 
> 
> 
> On Fri, Jun 3, 2016 at 9:09 AM Marcus Müller <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     Hi Eric,
> 
>     out of curiosity, since I can't do that on my clean CentOS 7
>     machines: have you managed to get thrift to build on a clean
>     installation?
> 
>     Best regards,
>     Marcus
> 
> 
>     On 03.06.2016 14:40, Eric Statzer wrote:
>>     In continuation of Martin's thread from last month [1], this is an
>>     update on testing of the "pybombs prefix init ~/path/to/prefix -R
>>     gnuradio-default" on a CentOS 7 host.
>>
>>     I submitted a pull request [2] to address an issue with building
>>     pyqwt5 on CentOS 7.  I haven't tested the change in my Docker farm
>>     yet, but I wanted to get the change out there to prompt
>>     discussion.  At this point, I'm not sure if any other common
>>     distros (Ubuntu 14.04?) build pyqwt5 from source, but I'm willing
>>     to add some more Docker containers to my Docker farm to do some
>>     regression testing on this if someone can confirm that this change
>>     is not limited to CentOS 7***.
>>
>>     I ran in to one other issue a couple weeks ago with building
>>     libosmo-dsp on CentOS 7.  The issue was related to trying to use a
>>     non-system version of automake to run autoreconf with the "-i"
>>     flag, but I'm unable to reproduce the issue now (go figure), so I
>>     need to do some more poking around.
>>
>>     Thanks,
>>     Eric
>>
>>
>>     *** On a side note, CentOS 7 is now available to me as a viable
>>     option, so I'm done fighting with CentOS 6.
>>
>>     [1] 
>> <https://lists.gnu.org/archive/html/discuss-gnuradio/2016-05/msg00242.html>https://lists.gnu.org/archive/html/discuss-gnuradio/2016-05/msg00242.html
>>     [2] https://github.com/gnuradio/gr-recipes/pull/32
>>
>>
>>
>>
>>     _______________________________________________
>>     Discuss-gnuradio mailing list
>>     address@hidden <mailto:address@hidden>
>>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
>     _______________________________________________
>     Discuss-gnuradio mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 




reply via email to

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