|Subject:||Re: [Discuss-gnuradio] Pybombs 2.0 woes|
|Date:||Sat, 5 Mar 2016 13:54:18 -0500|
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.
Following advice here I descended down a rabbit hole and tried to start again “pip uninstall pybombs”. Pip was not found.
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...
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.
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?
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.
uintptr_t is a standard type. See "man stdint.h".
A good motto is to assume nothing and please make sure you declare everything.
|[Prev in Thread]||Current Thread||[Next in Thread]|