You could also add your oot to the inventory file, add a recipe file,
and then use pybombs to compile your OOT to check if it's an env or
setup issue.
M
On 06/06/2016 11:08 AM, Richard Bell wrote:
> Hi Martin,
>
> Yes I did source the setup_env.sh file. I can call gnuradio-companion
> from comma
Hi Martin,
Yes I did source the setup_env.sh file. I can call gnuradio-companion from
command line and the base install works fine. It's only when compiling OOT
modules that I have issues.
I have not tried compiling without sudo, I will give it a shot.
Rich
On Mon, Jun 6, 2016 at 10:18 AM, Mar
Richard,
did you call your setup_env.sh before doing the compile? Also, you can
run cmake with -Wno-dev to remove some more annoying warnings.
On 06/04/2016 04:40 PM, Richard Bell wrote:
> Sure no problem. Here is the output when I try to build a brand new or
> pre-existing OOT module, notice the
Sure no problem. Here is the output when I try to build a brand new or
pre-existing OOT module, notice the cmake warnings:
rbell@rbell:~/Documents/pcodes/radio_devel/custom_grblocks/gr-add_tagged_stream_once/build$
cmake -DCMAKE_INSTALL_PREFIX=/home/rbell/Documents/grprefix/ ..
-- The CXX compiler
Hi Rich,
currently unable to access my Ubuntu VMs; could you copy&paste the build
log of your OOT? Also, I might be a bit paranoid, but could you verify
by "which gr_modtool" that you're really running the modtool you want?
Best regards,
Marcus
On 04.06.2016 17:51, Richard Bell wrote:
> Since I
Since I didn't get much feedback when I brought this up a few weeks ago, I want
to bring it up again to make sure you all see it. After using the default
pybombs command to build a clean install on Ubuntu 16.04, everything worked
fine except that I can't get gr_modtool working. No OOT Modules I
On Fri, Jun 3, 2016 at 10:19 AM Marcus Müller
wrote:
> 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 wish that was true! First of all, we need to find a better way to fix
> that then to build libtool on p
Marcus' changes were well warranted; the increased version reqs for
pkg-config and libtool caused *every* user to rebuild those tools from
source for every prefix, even Ubuntu 14.04 users. That was just
excessive. See my comment on special treatment of CentOS in my other
email in this thread.
Chee
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 to
> 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 wish that was true! First of all, we need to find a better way to fix
that then to build libtool on practically all platforms from source.
You really don't need l
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 >=
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
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
13 matches
Mail list logo
