Hi Mike,
I'm not overly involved with PyBOMBS myself, but just to "catch" you
right now:
On 05.03.2016 16:20, Mike Willis wrote:
I just wasted an hour or so trying to get
this to work. Clearly it is still early beta but with promise.
The first time I tried I got as far as the UHD install, which
crashed with an uninformative error 2.
Huh, that's uninformative, indeed.
I think there is some implicit assumption
going on in the developers head that non developers might
understand what is going on, or know how to find out what that
is.
Not really, but it's kind of that something like that usually sparks
my curiosity, so personally, I might have a pretty high tolerance
for that kind of trouble :D
Following advice here I descended down a
rabbit hole and tried to start again “pip uninstall pybombs”.
Pip was not found.
Uninstalling pybombs via pip only makes sense if you've installed it
via pip ("pip install pybombs"). Seemingly, you've either gotten
PyBombs through different means, so investigating pip doesn't really
make sense, or something uninstalled pip after you've installed it,
and installed Pybombs with it. That would be strange.
Pip and by the way, its actually called
“python-pip” if you can’t find it,
Please don't confuse the program name and the executable of the same
name, pip, with the name of the package in which Ubuntu ships it
(python-pip).
can be installed from apt-get install
python-pip. After uninstalling pybombs with pip I tried to
re-install with pip and now I get almost nowhere as “pip list”
generates an error. So I have uninstalled pip and all is well
again.
That has fixed the pip problem but not the
UHD installation crash, but as a by product the error messages
have become more verbose – and guess what? The problem is an
undeclared type. THIS SAME ISSUE WITH UNDEFINED TYPES
(shout so it sinks in, then repeat because it didn’t) THIS
SAME ISSUE WITH UNDEFINED TYPES that has been
around for over a YEAR in UHD and in this case
rx_dsp_core_200.cpp.
There is no such issue I know of. Now, that doesn't mean there's no
issue, it just means that none of the other users I've talked to nor
myself encountered it. However, probabilistically speaking, that's
indicative of something being wrong with your system...
Every so often I point it out and someone
fixes it and later on someone else (I wonder if this is the
same person who broke it last time) then adds some new code
somewhere else recreating the same errors. In this case its
uintptr_t that is not declared.
Um, sorry, I don't even see uintptr_t in rx_dsp_core_200.cpp, and
I've searched through its file history: It never occurred there. So
to research this issue, I'll need your full "make" output. Maybe
your version of Ubuntu fell off the testing bandwagon: which version
of Ubuntu are you using?
A good motto is to assume nothing and
please make sure you declare everything.
uintptr_t is a standard type. See "man stdint.h".
Best regards,
and hoping we can figure out what goes wrong here,
Marcus
|