rx_time is the time something upstream was received. This could be the
time of the first sample received by a USRP:
https://gnuradio.org/doc/doxygen/classgr_1_1uhd_1_1usrp__source.html#a8ba918061af928ee7c01e7124580eb82
rx_time could also be the time a packet was received, or could be set by
other blocks.
There is a utility called gr_read_file_metadata that installs with GR,
but I haven't tried it yet.
On 01/31/2018 05:37 PM, Zhongyuan Zhao wrote:
> Hi
>
> I have several questions regarding the rx_time in the metadata file
> sink, https://gnuradio.org/doc/doxygen/page_metadata.html
>
> 1) What is exactly the timestamp? The moment first sample is recorded on
> the hard drive?
> 2) Is there an example to convert rx_time to readable format?
> 3) Is there an way to timestamp the IQ data at the moment they are
> generated by USRP?
>
> Thanks.
> Zhongyuan Zhao
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Wednesday, January 31, 2018
[Discuss-gnuradio] Timestamp 'rx_time' in Metadata
Hi
I have several questions regarding the rx_time in the metadata file sink, https://gnuradio.org/doc/doxygen/page_metadata.html
1) What is exactly the timestamp? The moment first sample is recorded on the hard drive?
2) Is there an example to convert rx_time to readable format?
3) Is there an way to timestamp the IQ data at the moment they are generated by USRP?
Zhongyuan Zhao
Re: [Discuss-gnuradio] GNU Radio Project Leadership Updates
Thank you Jonathan. I hope you have more time to enjoy your airplane and amateur radio!
Welcome to all the other "old" new people taking on great roles. We appreciate it.
Bob
On Wed, Jan 31, 2018 at 3:24 PM, Ben Hilburn <bhilburn@gnuradio.org> wrote:
BenWe have a strong core team of experienced GNU Radio developers and community members, and I'm really excited about the work that will get done over the coming months. If you want to get involved, please don't hesitate to reach out! We love working with new contributors. And, as always, if you have any questions, just let us know.Our major priorities in the near-term include integrating the latest pull requests, publishing a clear process for community suggestions & contributions to the project, and getting to the long-awaited 3.8 release. If you're interested in these topics, keep an eye on the list and IRC! You'll start to see some announcements and activity very shortly.My position leading the project and Foundation remains unchanged, as do the roles of Martin Braun (Community Manager, PyBOMBS maintainer, Foundation Officer), and Nathan West (VOLK maintainer). While Andrej and Derek are expanding their development roles, Andrej will also continue as our web & devops infrastructure admin, and Derek will continue to organize GRCon18. Felix Wunsch will continue leading GNU Radio's participation in GSoC & SOCIS.As Johnathan transitions to his new role, well known developers in the community will be taking on expanded responsibilities. Marcus Mueller will become the Project Maintainer, responsible for merging, tagging, and generally maintaining the codebase. Derek Kozel, Bastian Bloessl, Andrej Rode, Philip Balister, and Nate Temple will become Project Officers, taking on various development and community efforts to keep the project moving forward.First, our Chief Architect and Foundation CTO, Johnathan Corgan, is moving into a new role as a Technical Advisor for the project. He will no longer be leading the project's technical development, but will remain part of the project leadership, sharing his technical knowledge and guidance. Johnathan has been a member of the GNU Radio project for 12 years, and served as the Project Maintainer for much of that. Additionally, for many years GNU Radio's infrastructure only existed because Johnathan paid for them with his own funds. Johnathan's contributions and leadership have been critical to GNU Radio's tremendous success, and the he deserves significant credit for the work he has done for the project and community.Hi all!As usual, there is a lot going on in the project and community, including GSOC & SOCIS, GRCon planning, and new development. There are also some big changes happening in the project leadership that I want to announce.Here's a note from Johnathan, himself, about the change:I've watched GNU Radio grow from its origins in the enthusiast community to a mainstream tool used extensively for government, academic, and commercial wireless research and applications. To have helped steward its design and implementation over the last decade, especially as an open source project with a purely volunteer community, has put me in contact with many talented and creative developers. Finally, teaching almost a hundred GNU Radio courses and consulting on GNU Radio projects in over a dozen countries has been the highlight of my career.
While I will continue to engage with users and provide technical assistance to the GNU Radio project, its forward growth depends on new leadership and commitment. I look forward to seeing what's next.Lastly, I would like to once again publicly thank Johnathan for all of his hard work and contributions as a leader in our community over the last 12 years!Happy Hacking,
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Bob McGwier
Founder, Federated Wireless, Inc
Founder and Technical Advisor, HawkEye 360, Inc
Research Professor Virginia Tech
Chief Scientist: The Ted and Karyn Hume Center for National Security and Technology
Senior Member IEEE, Facebook: N4HYBob, ARS: N4HY
Faculty Advisor Virginia Tech Amateur Radio Assn, Trustee K4KDJ
Director of AMSAT
Member of PVRC (Roanoke-Blacksburg), TAPR, life member of ARRL and AMSAT, NRVR.ORG (Rocketry)
[Discuss-gnuradio] QT GUI Frequency Sink Noise Floor
Hi,
I'm an Electrical Engineering Technology teacher and I like to use GNU Radio in my classrom for demos and labs.
Today, while trying to explain the relation between the noise floor on a frequency sprectrum and the RMS value of the same signal (noise), I realised that the QT GUI Frequency Sink noise floor is off.
When I connect a Noise source (amplitude of 1) to a QT GUI Frequency Sink, the noise flloor is -33 dB (window = none, fft size = 1024). I was expecting a noise floor of -30 dB as 1024 bin means that the 0dB total power is spread in 1024 bins (which gives -30dB).
For fun, I have switched the flowgraph to WX and used the FFT sink. The noise floor on the WX FFT sink was -30 dB as expected.
Anyone knows where the 3dB different comes from?
Thanks,
Frédéric
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
I'm an Electrical Engineering Technology teacher and I like to use GNU Radio in my classrom for demos and labs.
Today, while trying to explain the relation between the noise floor on a frequency sprectrum and the RMS value of the same signal (noise), I realised that the QT GUI Frequency Sink noise floor is off.
When I connect a Noise source (amplitude of 1) to a QT GUI Frequency Sink, the noise flloor is -33 dB (window = none, fft size = 1024). I was expecting a noise floor of -30 dB as 1024 bin means that the 0dB total power is spread in 1024 bins (which gives -30dB).
For fun, I have switched the flowgraph to WX and used the FFT sink. The noise floor on the WX FFT sink was -30 dB as expected.
Anyone knows where the 3dB different comes from?
Thanks,
Frédéric
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] GNU Radio Project Leadership Updates
Hi all!
As usual, there is a lot going on in the project and community, including GSOC & SOCIS, GRCon planning, and new development. There are also some big changes happening in the project leadership that I want to announce.Here's a note from Johnathan, himself, about the change:
I've watched GNU Radio grow from its origins in the enthusiast community to a mainstream tool used extensively for government, academic, and commercial wireless research and applications. To have helped steward its design and implementation over the last decade, especially as an open source project with a purely volunteer community, has put me in contact with many talented and creative developers. Finally, teaching almost a hundred GNU Radio courses and consulting on GNU Radio projects in over a dozen countries has been the highlight of my career.
While I will continue to engage with users and provide technical assistance to the GNU Radio project, its forward growth depends on new leadership and commitment. I look forward to seeing what's next.
Lastly, I would like to once again publicly thank Johnathan for all of his hard work and contributions as a leader in our community over the last 12 years!
Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
On 01/31/2018 03:16 PM, Sylvain Munaut wrote:
> Hi,
>
> * You can just use 0.0 / 0.0 as the default. Those value are only
> really used if you don't use the message system and just want a fixed
> / known manually set correction. Once the first message is received,
> those value are overwritten
>
> * As stated the time constant is in samples.
>
> * The 'optimize' block only really works when you have some narrow
> band signals distributed around the spectrums. It will fail
> _miserably_ if you have a single wideband signal centered around DC
> ...
>
> Cheers,
>
> Sylvain
Indeed, I find that if I use the osmocom IQ-balance code on radio
astronomy "signals" that it produces horrible results in interferometry
applications, as
it never really "converges", and adds significant long-time-scale
phase-noise, so I disable it.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> Hi,
>
> * You can just use 0.0 / 0.0 as the default. Those value are only
> really used if you don't use the message system and just want a fixed
> / known manually set correction. Once the first message is received,
> those value are overwritten
>
> * As stated the time constant is in samples.
>
> * The 'optimize' block only really works when you have some narrow
> band signals distributed around the spectrums. It will fail
> _miserably_ if you have a single wideband signal centered around DC
> ...
>
> Cheers,
>
> Sylvain
Indeed, I find that if I use the osmocom IQ-balance code on radio
astronomy "signals" that it produces horrible results in interferometry
applications, as
it never really "converges", and adds significant long-time-scale
phase-noise, so I disable it.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
Hi,
* You can just use 0.0 / 0.0 as the default. Those value are only
really used if you don't use the message system and just want a fixed
/ known manually set correction. Once the first message is received,
those value are overwritten
* As stated the time constant is in samples.
* The 'optimize' block only really works when you have some narrow
band signals distributed around the spectrums. It will fail
_miserably_ if you have a single wideband signal centered around DC
...
Cheers,
Sylvain
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
* You can just use 0.0 / 0.0 as the default. Those value are only
really used if you don't use the message system and just want a fixed
/ known manually set correction. Once the first message is received,
those value are overwritten
* As stated the time constant is in samples.
* The 'optimize' block only really works when you have some narrow
band signals distributed around the spectrums. It will fail
_miserably_ if you have a single wideband signal centered around DC
...
Cheers,
Sylvain
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] LoRa implementation (resuming an old topic)
Hi Alberto,
On 2018-01-31 20:00, Alberto Trentadue wrote:
> Back in October 2015 I dropped a question to the list, asking if
> anybody had attempted implementing LoRa
> modulation using GNURadio. At that time Marcus Muller kindly replied,
> suggesting me to take such endeavour.
> Unfortunately, such project did not get enough attention and I had to
> drop it.
>
> Did anyone else try such thing - just to avoid to reinvent the wheel?
>
there is a module called `gr-lora` you can find here [0].
There is also at least one presentation about it at GRCon16. You can
find GRCon videos at the YouTube channel of GNU Radio [1].
Cheers,
Andrej
[0] https://github.com/BastilleResearch/gr-lora
[1] https://www.youtube.com/c/GNURadioProject
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
On 2018-01-31 20:00, Alberto Trentadue wrote:
> Back in October 2015 I dropped a question to the list, asking if
> anybody had attempted implementing LoRa
> modulation using GNURadio. At that time Marcus Muller kindly replied,
> suggesting me to take such endeavour.
> Unfortunately, such project did not get enough attention and I had to
> drop it.
>
> Did anyone else try such thing - just to avoid to reinvent the wheel?
>
there is a module called `gr-lora` you can find here [0].
There is also at least one presentation about it at GRCon16. You can
find GRCon videos at the YouTube channel of GNU Radio [1].
Cheers,
Andrej
[0] https://github.com/BastilleResearch/gr-lora
[1] https://www.youtube.com/c/GNURadioProject
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] LoRa implementation (resuming an old topic)
Hi all
Back in October 2015 I dropped a question to the list, asking if anybody had attempted implementing LoRa
modulation using GNURadio. At that time Marcus Muller kindly replied, suggesting me to take such endeavour.
Unfortunately, such project did not get enough attention and I had to drop it.
Now I am dealing with testing LoRa gateways, possibly without the need of LoRa client cards. necessarily. So I would like to use my USRP to make initial LoRa test at 868 MHz.
Did anyone else try such thing - just to avoid to reinvent the wheel?
Thank you
Alberto
[Discuss-gnuradio] Call for GRCon18 Committee Volunteers
Hello,
Regular as clockwork the new year has come and it is time to prepare for GNU Radio Conference 2018! GRCon17 was another great success continuing the trend of growing in size and scope. We had 40% more attendees than in 2016 and 96.9% of attendees who responded to the survey gave the event a four or five out of five overall rating. The survey also provided some very useful feedback about what the best parts of the conference were and how to even better serve the needs and wants of the community.
Planning GRCon is a significant undertaking, and is only possible each year because of our community volunteers. You can volunteer at a variety of levels, taking on whatever responsibilities your time & availability affords. It's a great experience, and a good opportunity to get more deeply involved with the GNU Radio project & community.
If you are interested in joining the GRCon18 Committee, or have any questions, please let us know by emailing grcon@gnuradio.org.
Thanks,
Derek
Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
1. Add a throttle after the source.
2. You are feeding the optimizer and the balancer from the original
signal. They need to be connected to the output of the imbalance generator.
3. Whatever the scale of magnitude is in the imbalance generator, 1.0 is
too small to see on the time plot.
4. The time plots will look different if the phase is rotated, so
different is not necessarily wrong.
5. Add a slider to control magnitude, and you can see the optimizer adjust.
On 01/31/2018 09:21 AM, kokosz wrote:
> This is exactly what I am doing, but restored signal looks very weird
> (its real part is close to zero). I have attached example *grc file
> showing the problem.
>
> Dnia 31 stycznia 2018 12:34 Jeff Long <willcode4@gmail.com> napisał(a):
>
> If you put 0 in the manual fields and wire
>
> src->optimize->iqbal
>
> and
>
> src->iqbal
>
> it seems to work fine. Do you have a GRC file?
>
> "period" is some sort of time constant, in samples. If you set it to
> samp_rate, optimization will happen within a second. Smaller values for
> faster response up to a point.
>
> On 01/31/2018 05:54 AM, kokosz wrote:
>
> Dear all,
>
> It looks like IQ imbalance is causing problems in my
> application, as I
> was able to simulate real-world-like problems after adding "IQ
> Imbalance
> Generator" to my GRC flowgraph. So, after simulating this
> imbalance, I
> wanted to get rid of it with the help of "IQ Bal Optimize" and
> "IQ Bal
> Fix" combo. Unfortunately, I can't get it work.
>
> As far as I understand, "IQ Bal Optimize" is automatically
> detecting
> settings (i.e. magnitude and phase correction values) for "IQ
> Bal Fix"
> and pass it to the latter block via message connection called
> "iqbal_corr". Is this is true, I don't understand why I have to
> manually
> set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot
> run the
> flowgraph because of empty fields). I think that these fields
> were meant
> for making manual fix possible, but when using "IQ Bal
> Optimize"/"IQ Bal
> Fix" combo, message connection should be all what is necessary,
> right?
> Also, because of lack of detailed documentation, I am not sure
> how to
> interpret "Period" field in IQ Bal Optimize - what units are
> expected here?
>
> I am using GRC v3.7.11, compiled from source files few days ago.
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
This is exactly what I am doing, but restored signal looks very weird (its real part is close to zero). I have attached example *grc file showing the problem.
Dnia 31 stycznia 2018 12:34 Jeff Long <willcode4@gmail.com> napisał(a):
If you put 0 in the manual fields and wiresrc->optimize->iqbalandsrc->iqbalit seems to work fine. Do you have a GRC file?"period" is some sort of time constant, in samples. If you set it tosamp_rate, optimization will happen within a second. Smaller values forfaster response up to a point.On 01/31/2018 05:54 AM, kokosz wrote:Dear all,It looks like IQ imbalance is causing problems in my application, as Iwas able to simulate real-world-like problems after adding "IQ ImbalanceGenerator" to my GRC flowgraph. So, after simulating this imbalance, Iwanted to get rid of it with the help of "IQ Bal Optimize" and "IQ BalFix" combo. Unfortunately, I can't get it work.As far as I understand, "IQ Bal Optimize" is automatically detectingsettings (i.e. magnitude and phase correction values) for "IQ Bal Fix"and pass it to the latter block via message connection called"iqbal_corr". Is this is true, I don't understand why I have to manuallyset "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run theflowgraph because of empty fields). I think that these fields were meantfor making manual fix possible, but when using "IQ Bal Optimize"/"IQ BalFix" combo, message connection should be all what is necessary, right?Also, because of lack of detailed documentation, I am not sure how tointerpret "Period" field in IQ Bal Optimize - what units are expected here?I am using GRC v3.7.11, compiled from source files few days ago._______________________________________________Discuss-gnuradio mailing list_______________________________________________Discuss-gnuradio mailing list
Re: [Discuss-gnuradio] gnu radio installation on Mac via MacPorts
Thanks for reporting back, Vipin, and your creative solution. Sometimes starting over is the way to go ;)
A strange note: the "rev-upgrade" logfile was clean; no errors or issues found beyond the usual innocuous ones. I've no idea why port thought uhd was broken the final run-through.
Anyway: Good catch on the gpsd issue; I'm glad we got it fixed quickly! You're very welcome for the support! - MLD
On Wed, Jan 31, 2018, at 2:28 AM, Vipin Sharma wrote:
Ok, I tried another attempt by completely removing the MacPorts and restarting. This time it worked!sudo port -fp uninstall installedsudo rm -rf /opt/local /Applications/DarwinPorts /Applications/MacPorts /Library/LaunchDaemons/org.macports.* /Library/Receipts/DarwinPorts*.pkg /Library/Receipts/MacPorts*.pkg /Library/StartupItems/DarwinPortsStartup /Library/Tcl/darwinports1.0 /Library/Tcl/macports1.0 ~/.macports
sudo port selfupdate
sudo port install gnuradio
I got segmentation fault when I tried this:
uhd_fft -f 868M -s 10M
but then after trying
sudo port select --set python python27
uhd_fft works fine.Thanks for your support!
Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
If you put 0 in the manual fields and wire
src->optimize->iqbal
and
src->iqbal
it seems to work fine. Do you have a GRC file?
"period" is some sort of time constant, in samples. If you set it to
samp_rate, optimization will happen within a second. Smaller values for
faster response up to a point.
On 01/31/2018 05:54 AM, kokosz wrote:
> Dear all,
>
> It looks like IQ imbalance is causing problems in my application, as I
> was able to simulate real-world-like problems after adding "IQ Imbalance
> Generator" to my GRC flowgraph. So, after simulating this imbalance, I
> wanted to get rid of it with the help of "IQ Bal Optimize" and "IQ Bal
> Fix" combo. Unfortunately, I can't get it work.
>
> As far as I understand, "IQ Bal Optimize" is automatically detecting
> settings (i.e. magnitude and phase correction values) for "IQ Bal Fix"
> and pass it to the latter block via message connection called
> "iqbal_corr". Is this is true, I don't understand why I have to manually
> set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run the
> flowgraph because of empty fields). I think that these fields were meant
> for making manual fix possible, but when using "IQ Bal Optimize"/"IQ Bal
> Fix" combo, message connection should be all what is necessary, right?
> Also, because of lack of detailed documentation, I am not sure how to
> interpret "Period" field in IQ Bal Optimize - what units are expected here?
>
> I am using GRC v3.7.11, compiled from source files few days ago.
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
src->optimize->iqbal
and
src->iqbal
it seems to work fine. Do you have a GRC file?
"period" is some sort of time constant, in samples. If you set it to
samp_rate, optimization will happen within a second. Smaller values for
faster response up to a point.
On 01/31/2018 05:54 AM, kokosz wrote:
> Dear all,
>
> It looks like IQ imbalance is causing problems in my application, as I
> was able to simulate real-world-like problems after adding "IQ Imbalance
> Generator" to my GRC flowgraph. So, after simulating this imbalance, I
> wanted to get rid of it with the help of "IQ Bal Optimize" and "IQ Bal
> Fix" combo. Unfortunately, I can't get it work.
>
> As far as I understand, "IQ Bal Optimize" is automatically detecting
> settings (i.e. magnitude and phase correction values) for "IQ Bal Fix"
> and pass it to the latter block via message connection called
> "iqbal_corr". Is this is true, I don't understand why I have to manually
> set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run the
> flowgraph because of empty fields). I think that these fields were meant
> for making manual fix possible, but when using "IQ Bal Optimize"/"IQ Bal
> Fix" combo, message connection should be all what is necessary, right?
> Also, because of lack of detailed documentation, I am not sure how to
> interpret "Period" field in IQ Bal Optimize - what units are expected here?
>
> I am using GRC v3.7.11, compiled from source files few days ago.
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
Dear all,
It looks like IQ imbalance is causing problems in my application, as I was able to simulate real-world-like problems after adding "IQ Imbalance Generator" to my GRC flowgraph. So, after simulating this imbalance, I wanted to get rid of it with the help of "IQ Bal Optimize" and "IQ Bal Fix" combo. Unfortunately, I can't get it work.
As far as I understand, "IQ Bal Optimize" is automatically detecting settings (i.e. magnitude and phase correction values) for "IQ Bal Fix" and pass it to the latter block via message connection called "iqbal_corr". Is this is true, I don't understand why I have to manually set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run the flowgraph because of empty fields). I think that these fields were meant for making manual fix possible, but when using "IQ Bal Optimize"/"IQ Bal Fix" combo, message connection should be all what is necessary, right? Also, because of lack of detailed documentation, I am not sure how to interpret "Period" field in IQ Bal Optimize - what units are expected here?
I am using GRC v3.7.11, compiled from source files few days ago.
As far as I understand, "IQ Bal Optimize" is automatically detecting settings (i.e. magnitude and phase correction values) for "IQ Bal Fix" and pass it to the latter block via message connection called "iqbal_corr". Is this is true, I don't understand why I have to manually set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run the flowgraph because of empty fields). I think that these fields were meant for making manual fix possible, but when using "IQ Bal Optimize"/"IQ Bal Fix" combo, message connection should be all what is necessary, right? Also, because of lack of detailed documentation, I am not sure how to interpret "Period" field in IQ Bal Optimize - what units are expected here?
I am using GRC v3.7.11, compiled from source files few days ago.
Tuesday, January 30, 2018
Re: [Discuss-gnuradio] gnu radio installation on Mac via MacPorts
Ok, I tried another attempt by completely removing the MacPorts and restarting. This time it worked!
sudo port -fp uninstall installed
sudo rm -rf /opt/local /Applications/DarwinPorts /Applications/MacPorts /Library/LaunchDaemons/org.macports.* /Library/Receipts/DarwinPorts*.pkg /Library/Receipts/MacPorts*.pkg /Library/StartupItems/DarwinPortsStartup /Library/Tcl/darwinports1.0 /Library/Tcl/macports1.0 ~/.macports
sudo port selfupdate
sudo port install gnuradio
I got segmentation fault when I tried this:
uhd_fft -f 868M -s 10M
but then after trying
sudo port select --set python python27
uhd_fft works fine.
Thanks for your support!
Vipin
On Tue, Jan 30, 2018 at 7:42 PM, Vipin Sharma <vipinsharma@photonpace.com> wrote:
Alright, I gave it a try after your fix just now. Still not successful. Here is what I do/get. At first it seemed uhd installation went successful but while building gnuradio something goes wrong. I also tried collecting the uhd_rev.txt file from your earlier comment. I will send that file directly to you in the next email.mac01:~ emwaves$ sudo port selfupdate
Password:
---> Updating MacPorts base sources using rsync
MacPorts base version 2.4.2 installed,
MacPorts base version 2.4.2 downloaded.
---> Updating the ports tree
---> MacPorts base is already the latest version
The ports tree has been updated. To upgrade your installed ports, you should run
port upgrade outdated
mac01:~ emwaves$ sudo port uninstall gnuradio
---> Deactivating gnuradio @3.7.11_6+docs+grc+jack+
log4cpp+logging+portaudio+ qtgui+sdl+swig+uhd+wavelet+ zeromq ---> Cleaning gnuradio
---> Uninstalling gnuradio @3.7.11_6+docs+grc+jack+
log4cpp+logging+portaudio+ qtgui+sdl+swig+uhd+wavelet+ zeromq ---> Cleaning gnuradio
mac01:~ emwaves$ sudo port uninstall uhd
---> Deactivating uhd @3.10.2.0_1+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
---> Uninstalling uhd @3.10.2.0_1+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
mac01:~ emwaves$ sudo port install gnuradio
---> Computing dependencies for gtk2
---> Fetching archive for gtk2
---> Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.
x86_64.tbz2 from https://packages.macports.org/ gtk2 ---> Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.
x86_64.tbz2.rmd160 from https://packages.macports.org/ gtk2 ---> Installing gtk2 @2.24.32_0+x11
---> Cleaning gtk2
---> Computing dependencies for gtk2
---> Deactivating gtk2 @2.24.31_0+x11
---> Cleaning gtk2
---> Activating gtk2 @2.24.32_0+x11
---> Cleaning gtk2
---> Computing dependencies for py27-zmq
---> Fetching archive for py27-zmq
---> Attempting to fetch py27-zmq-16.0.4_0.darwin_16.
x86_64.tbz2 from https://packages.macports.org/ py27-zmq ---> Attempting to fetch py27-zmq-16.0.4_0.darwin_16.
x86_64.tbz2.rmd160 from https://packages.macports.org/ py27-zmq ---> Installing py27-zmq @16.0.4_0
---> Cleaning py27-zmq
---> Computing dependencies for py27-zmq
---> Deactivating py27-zmq @16.0.3_0
---> Cleaning py27-zmq
---> Activating py27-zmq @16.0.4_0
---> Cleaning py27-zmq
---> Computing dependencies for gnuradio
The following dependencies will be installed: uhd
Continue? [Y/n]: Y
---> Fetching archive for uhd
---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test.darwin_16.x86_ 64.tbz2 from https://packages.macports.org/ uhd ---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test.darwin_16.x86_ 64.tbz2 from http://sea.us.packages. macports.org/macports/ packages/uhd ---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test.darwin_16.x86_ 64.tbz2 from http://ywg.ca.packages. macports.org/mirror/macports/ packages/uhd ---> Fetching distfiles for uhd
---> Verifying checksums for uhd
---> Extracting uhd
---> Applying patches to uhd
---> Configuring uhd
---> Building uhd
---> Staging uhd into destroot
---> Installing uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Activating uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
---> Fetching archive for gnuradio
---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+
jack+log4cpp+logging+ portaudio+qtgui+sdl+swig+uhd+ wavelet+zeromq.darwin_16.x86_ 64.tbz2 from https://packages.macports.org/ gnuradio ---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+
jack+log4cpp+logging+ portaudio+qtgui+sdl+swig+uhd+ wavelet+zeromq.darwin_16.x86_ 64.tbz2 from http://sea.us.packages. macports.org/macports/ packages/gnuradio ---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+
jack+log4cpp+logging+ portaudio+qtgui+sdl+swig+uhd+ wavelet+zeromq.darwin_16.x86_ 64.tbz2 from http://ywg.ca.packages. macports.org/mirror/macports/ packages/gnuradio ---> Fetching distfiles for gnuradio
---> Verifying checksums for gnuradio
---> Extracting gnuradio
---> Applying patches to gnuradio
---> Configuring gnuradio
---> Building gnuradio
---> Staging gnuradio into destroot
---> Installing gnuradio @3.7.11_6+docs+grc+jack+
log4cpp+logging+portaudio+ qtgui+sdl+swig+uhd+wavelet+ zeromq ---> Activating gnuradio @3.7.11_6+docs+grc+jack+
log4cpp+logging+portaudio+ qtgui+sdl+swig+uhd+wavelet+ zeromq ---> Cleaning gnuradio
---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 76 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: uhd @3.10.2.0+docs+examples+gpsd+
libusb+manpages+manual+ python27+test Continue? [Y/n]: Y
---> Computing dependencies for gpsd
---> Fetching archive for gpsd
---> Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.
tbz2 from https://packages.macports.org/ gpsd ---> Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.
tbz2.rmd160 from https://packages.macports.org/ gpsd ---> Installing gpsd @3.17_1
---> Cleaning gpsd
---> Computing dependencies for gpsd
---> Deactivating gpsd @3.17_0
---> Cleaning gpsd
---> Activating gpsd @3.17_1
---> Cleaning gpsd
---> Computing dependencies for uhd
---> Cleaning uhd
---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 76 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
---> Rebuilding in order
uhd @3.10.2.0 +docs+examples+gpsd+libusb+
manpages+manual+python27+test ---> Computing dependencies for uhd
---> Fetching distfiles for uhd
---> Verifying checksums for uhd
---> Extracting uhd
---> Applying patches to uhd
---> Configuring uhd
---> Building uhd
---> Staging uhd into destroot
---> Unable to uninstall uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test, the following ports depend on it: ---> gnuradio @3.7.11_6+docs+grc+jack+
log4cpp+logging+portaudio+ qtgui+sdl+swig+uhd+wavelet+ zeromq Warning: Uninstall forced. Proceeding despite dependencies.
---> Deactivating uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
---> Uninstalling uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
---> Computing dependencies for uhd
---> Installing uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Activating uhd @3.10.2.0_2+docs+examples+
gpsd+libusb+manpages+manual+ python27+test ---> Cleaning uhd
---> Updating database of binaries
---> Scanning binaries for linking errors
---> No broken files found.
---> Some of the ports you installed have notes:
gpsd has the following notes:
The xgps variant is now needed to get the xgps and xgpsspeed programs.
mac01:~ emwaves$
On Tue, Jan 30, 2018 at 6:02 AM, Michael Dickens <michael.dickens@ettus.com> wrote:I pushed fixes into MacPorts this morning. Will be live by around 9:30 AM US/Eastern (about 30 minutes from now). You will need to "selfupdate" or "sync" to get the changes. Please let me know (here or off list) success or failure. Cheers! - MLDOn Mon, Jan 29, 2018, at 8:54 PM, Vipin Sharma wrote:Great; thank you. I will just wait for your fix.
Re: [Discuss-gnuradio] gr-bluetooth installation issue
In the directory
./gr-bluetooth/python
try changing the line
import bluetooth.swig as bluetooth
to
import _gr_bluetooth as bluetooth
in the file
qa_gr_bluetooth_multi_sniffer.py
-- Cinaed
On 01/30/2018 05:03 PM, Suman Bhunia wrote:
> Hi,
>
> I want to use gr-bluetooth to sniff packets. I have installed
> gnuradio3.7.9, uhd on Ubuntu 16.04. I am encountering some error
> installing gr-bluetooth it. When I use the cmake command, I obtain the
> following output:
>
>
> -- The CXX compiler identification is GNU 5.4.0
> -- The C compiler identification is GNU 5.4.0
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Build type not specified: defaulting to release.
> -- Boost version: 1.58.0
> -- Found the following Boost libraries:
> -- filesystem
> -- system
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
> Checking for GNU Radio Module: RUNTIME
> -- Checking for module 'gnuradio-runtime'
> -- Found gnuradio-runtime, version 3.7.9
> * INCLUDES=/usr/include
> *
> LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
> -- Found GNURADIO_RUNTIME:
> /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_RUNTIME_FOUND = TRUE
> Checking for GNU Radio Module: BLOCKS
> -- Checking for module 'gnuradio-blocks'
> -- Found gnuradio-blocks, version 3.7.9
> * INCLUDES=/usr/include
> *
> LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
> -- Found GNURADIO_BLOCKS:
> /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_BLOCKS_FOUND = TRUE
> Checking for GNU Radio Module: FILTER
> -- Checking for module 'gnuradio-filter'
> -- Found gnuradio-filter, version 3.7.9
> * INCLUDES=/usr/include
> *
> LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
> -- Found GNURADIO_FILTER:
> /usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_FILTER_FOUND = TRUE
> -- Checking for module 'cppunit'
> -- Found cppunit, version 1.13.2
> -- Found CPPUNIT: /usr/lib/x86_64-linux-gnu/libcppunit.so;dl
> -- Found LIBBTBB: /usr/lib/x86_64-linux-gnu/libbtbb.so
> --
> -- Checking for module SWIG
> -- Found SWIG version 3.0.8.
> -- Found SWIG: /usr/bin/swig3.0
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so
> (found suitable version "2.7.12", minimum required is "2")
> -- Found PythonInterp: /usr/bin/python2 (found suitable version
> "2.7.12", minimum required is "2")
> -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE
> -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE - Success
> CMake Warning (dev) at
> /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
> (get_target_property):
> Policy CMP0026 is not set: Disallow use of the LOCATION target
> property.
> Run "cmake --help-policy CMP0026" for policy details. Use the
> cmake_policy
> command to set the policy and suppress this warning.
>
> The LOCATION property should not be read from target
> "gnuradio-bluetooth".
> Use the target name directly with add_custom_command, or use the
> generator
> expression $<TARGET_FILE>, as appropriate.
>
> Call Stack (most recent call first):
> python/CMakeLists.txt:44 (GR_ADD_TEST)
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> CMake Warning (dev) at
> /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
> (get_target_property):
> Policy CMP0045 is not set: Error on non-existent target in
> get_target_property. Run "cmake --help-policy CMP0045" for policy
> details.
> Use the cmake_policy command to set the policy and suppress this
> warning.
>
> get_target_property() called with non-existent target
> "/usr/bin/python2".
> Call Stack (most recent call first):
> python/CMakeLists.txt:44 (GR_ADD_TEST)
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> CMake Warning (dev) at
> /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
> (get_target_property):
> Policy CMP0045 is not set: Error on non-existent target in
> get_target_property. Run "cmake --help-policy CMP0045" for policy
> details.
> Use the cmake_policy command to set the policy and suppress this
> warning.
>
> get_target_property() called with non-existent target
> "/home/iot3/gr-bluetooth/python/qa_gr_bluetooth_multi_sniffer.py".
> Call Stack (most recent call first):
> python/CMakeLists.txt:44 (GR_ADD_TEST)
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> -- Found Doxygen: /usr/bin/doxygen (found version "1.8.11")
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /home/iot3/gr-bluetooth/build
>
>
>
> Output of 'make' command:
>
>
> [ 4%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/tun.cc.o
> <http://gnuradio-bluetooth.dir/tun.cc.o>
> [ 8%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/multi_block.cc.o
> <http://gnuradio-bluetooth.dir/multi_block.cc.o>
> [ 12%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/multi_hopper_impl.cc.o
> <http://gnuradio-bluetooth.dir/multi_hopper_impl.cc.o>
> [ 16%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/multi_LAP_impl.cc.o
> <http://gnuradio-bluetooth.dir/multi_LAP_impl.cc.o>
> [ 20%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/multi_sniffer_impl.cc.o
> <http://gnuradio-bluetooth.dir/multi_sniffer_impl.cc.o>
> [ 25%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/multi_UAP_impl.cc.o
> <http://gnuradio-bluetooth.dir/multi_UAP_impl.cc.o>
> [ 29%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/packet_impl.cc.o
> <http://gnuradio-bluetooth.dir/packet_impl.cc.o>
> [ 33%] Building CXX object
> lib/CMakeFiles/gnuradio-bluetooth.dir/piconet_impl.cc.o
> <http://gnuradio-bluetooth.dir/piconet_impl.cc.o>
> [ 37%] Linking CXX shared library libgnuradio-bluetooth.so
> [ 37%] Built target gnuradio-bluetooth
> Scanning dependencies of target gr_bluetooth_swig_doc
> [ 37%] Built target gr_bluetooth_swig_doc
> Scanning dependencies of target _gr_bluetooth_swig_tag
> [ 41%] Building CXX object
> swig/CMakeFiles/_gr_bluetooth_swig_tag.dir/_gr_bluetooth_swig_tag.cpp.o
> [ 45%] Linking CXX executable _gr_bluetooth_swig_tag
> [ 45%] Built target _gr_bluetooth_swig_tag
> [ 50%] Generating gr_bluetooth.tag
> Scanning dependencies of target gr_bluetooth_swig_2d0df
> [ 54%] Building CXX object
> swig/CMakeFiles/gr_bluetooth_swig_2d0df.dir/gr_bluetooth_swig_2d0df.cpp.o
> [ 58%] Linking CXX executable gr_bluetooth_swig_2d0df
> Swig source
> /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:148: Warning
> 314: 'print' is a python keyword, renaming to '_print'
> /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:241: Warning
> 314: 'print' is a python keyword, renaming to '_print'
> /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:332: Warning
> 314: 'print' is a python keyword, renaming to '_print'
> [ 58%] Built target gr_bluetooth_swig_2d0df
> Scanning dependencies of target _gr_bluetooth
> [ 62%] Building CXX object
> swig/CMakeFiles/_gr_bluetooth.dir/gr_bluetoothPYTHON_wrap.cxx.o
> [ 66%] Linking CXX shared module _gr_bluetooth.so
> [ 75%] Built target _gr_bluetooth
> Scanning dependencies of target pygen_swig_d9cb6
> [ 79%] Generating gr_bluetooth.pyc
> [ 83%] Generating gr_bluetooth.pyo
> [ 87%] Built target pygen_swig_d9cb6
> Scanning dependencies of target pygen_python_b3a7c
> [ 91%] Generating __init__.pyc
> [ 95%] Generating __init__.pyo
> [ 95%] Built target pygen_python_b3a7c
> Scanning dependencies of target pygen_apps_89140
> [100%] Shebangin btrx
> [100%] Built target pygen_apps_89140
>
>
>
> When I used make test command, I got the following output:
>
> Test project /home/iot3/gr-bluetooth/build
> Start 1: qa_gr_bluetooth_multi_sniffer
> 1/1 Test #1: qa_gr_bluetooth_multi_sniffer ....***Failed 0.07 sec
>
> 0% tests passed, 1 tests failed out of 1
>
> Total Test time (real) = 0.07 sec
>
> The following tests FAILED:
> 1 - qa_gr_bluetooth_multi_sniffer (Failed)
> Errors while running CTest
> Makefile:127: recipe for target 'test' failed
> make: *** [test] Error 8
>
>
> I was wondering if anyone could help me what would be a probable
> solution might be.
>
> Thanks,
> Suman
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnu radio installation on Mac via MacPorts
Alright, I gave it a try after your fix just now. Still not successful. Here is what I do/get. At first it seemed uhd installation went successful but while building gnuradio something goes wrong. I also tried collecting the uhd_rev.txt file from your earlier comment. I will send that file directly to you in the next email.
mac01:~ emwaves$ sudo port selfupdate
Password:
---> Updating MacPorts base sources using rsync
MacPorts base version 2.4.2 installed,
MacPorts base version 2.4.2 downloaded.
---> Updating the ports tree
---> MacPorts base is already the latest version
The ports tree has been updated. To upgrade your installed ports, you should run
port upgrade outdated
mac01:~ emwaves$ sudo port uninstall gnuradio
---> Deactivating gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
---> Cleaning gnuradio
---> Uninstalling gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
---> Cleaning gnuradio
mac01:~ emwaves$ sudo port uninstall uhd
---> Deactivating uhd @3.10.2.0_1+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
---> Uninstalling uhd @3.10.2.0_1+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
mac01:~ emwaves$ sudo port install gnuradio
---> Computing dependencies for gtk2
---> Fetching archive for gtk2
---> Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2 from https://packages.macports.org/gtk2
---> Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2.rmd160 from https://packages.macports.org/gtk2
---> Installing gtk2 @2.24.32_0+x11
---> Cleaning gtk2
---> Computing dependencies for gtk2
---> Deactivating gtk2 @2.24.31_0+x11
---> Cleaning gtk2
---> Activating gtk2 @2.24.32_0+x11
---> Cleaning gtk2
---> Computing dependencies for py27-zmq
---> Fetching archive for py27-zmq
---> Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2 from https://packages.macports.org/py27-zmq
---> Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2.rmd160 from https://packages.macports.org/py27-zmq
---> Installing py27-zmq @16.0.4_0
---> Cleaning py27-zmq
---> Computing dependencies for py27-zmq
---> Deactivating py27-zmq @16.0.3_0
---> Cleaning py27-zmq
---> Activating py27-zmq @16.0.4_0
---> Cleaning py27-zmq
---> Computing dependencies for gnuradio
The following dependencies will be installed: uhd
Continue? [Y/n]: Y
---> Fetching archive for uhd
---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from https://packages.macports.org/uhd
---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/uhd
---> Attempting to fetch uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/uhd
---> Fetching distfiles for uhd
---> Verifying checksums for uhd
---> Extracting uhd
---> Applying patches to uhd
---> Configuring uhd
---> Building uhd
---> Staging uhd into destroot
---> Installing uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Activating uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
---> Fetching archive for gnuradio
---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from https://packages.macports.org/gnuradio
---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/gnuradio
---> Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/gnuradio
---> Fetching distfiles for gnuradio
---> Verifying checksums for gnuradio
---> Extracting gnuradio
---> Applying patches to gnuradio
---> Configuring gnuradio
---> Building gnuradio
---> Staging gnuradio into destroot
---> Installing gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
---> Activating gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
---> Cleaning gnuradio
---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 76 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: uhd @3.10.2.0+docs+examples+gpsd+libusb+manpages+manual+python27+test
Continue? [Y/n]: Y
---> Computing dependencies for gpsd
---> Fetching archive for gpsd
---> Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2 from https://packages.macports.org/gpsd
---> Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2.rmd160 from https://packages.macports.org/gpsd
---> Installing gpsd @3.17_1
---> Cleaning gpsd
---> Computing dependencies for gpsd
---> Deactivating gpsd @3.17_0
---> Cleaning gpsd
---> Activating gpsd @3.17_1
---> Cleaning gpsd
---> Computing dependencies for uhd
---> Cleaning uhd
---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 76 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
---> Rebuilding in order
uhd @3.10.2.0 +docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Computing dependencies for uhd
---> Fetching distfiles for uhd
---> Verifying checksums for uhd
---> Extracting uhd
---> Applying patches to uhd
---> Configuring uhd
---> Building uhd
---> Staging uhd into destroot
---> Unable to uninstall uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test, the following ports depend on it:
---> gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
Warning: Uninstall forced. Proceeding despite dependencies.
---> Deactivating uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
---> Uninstalling uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
---> Computing dependencies for uhd
---> Installing uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Activating uhd @3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test
---> Cleaning uhd
---> Updating database of binaries
---> Scanning binaries for linking errors
---> No broken files found.
---> Some of the ports you installed have notes:
gpsd has the following notes:
The xgps variant is now needed to get the xgps and xgpsspeed programs.
mac01:~ emwaves$
On Tue, Jan 30, 2018 at 6:02 AM, Michael Dickens <michael.dickens@ettus.com> wrote:
I pushed fixes into MacPorts this morning. Will be live by around 9:30 AM US/Eastern (about 30 minutes from now). You will need to "selfupdate" or "sync" to get the changes. Please let me know (here or off list) success or failure. Cheers! - MLDOn Mon, Jan 29, 2018, at 8:54 PM, Vipin Sharma wrote:Great; thank you. I will just wait for your fix.
Subscribe to:
Comments (Atom)