-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NameError: name 'ieee802_11' is not defined, when loading wifi_loopback.grc #379
Comments
Maybe you didn't build the hierarchical block, i.e., open wifi_phy_hier.grc, click build, and reopen GRC? |
It's not possible to build because the gadgets are not found. Anyway I reconfigured distro python and removed the local python managed by asdf (I think it was conflicting since gnuradio use /usr/bin/python3): But now I have another problem that maybe is easier to catch:
Both gr-foo and gr-ieee802_11 were configured with The environment is also configured:
Any ideas? |
That looks like a PyBind version conflict. Can you please try the one that comes with your distro. |
This is done already, but not working:
Both |
This shows that you have pybind11 from you package manager installed. Please also make sure that there is no other version in your user environment or some other Python package manager that may be picked up during the compilation of GNU Radio or the OOT module. |
Unfortunately this is not working for me. |
Again, your output shows that you have pybind from your package manager installed. It does not show that there is not other version from asdf (or whatever you used) or pip or virtualenv or ... I'm pretty sure either GNU Radio or the OOT or both were not compiled with the correct pybind version. |
Regarding pybind I already showed that it was installed from package manager and there is not other version installed:
I unalias and unsourced every asdf python reference, so both pybind and gnuradio are from package manager. I did not compile gnuradio, but installed from Ubuntu repository.
In case of gr-ieee802_11 I compiled as:
And then:
Regarding the line
|
All I can say is that I had this exact problem and it turned out to be a pybind issue. The exact same problem is also identified as a pybind issue here: https://lists.gnu.org/archive/html/discuss-gnuradio/2021-05/msg00056.html Please try to compile any other GNU Radio module. If other modules work, let me know. Otherwise, please write to the GNU Radio mailing list. |
Hallo there.
I know this is a very annoying error and I'm sorry for opening issue about that. I tried everything I could think of.
The error I'm getting is this one:
The gnuradio-companion print:
![image](https://private-user-images.githubusercontent.com/8737680/244798702-5ebc920d-d4a0-49c7-ae53-82be1d577370.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDQxMjksIm5iZiI6MTcyNjE0MzgyOSwicGF0aCI6Ii84NzM3NjgwLzI0NDc5ODcwMi01ZWJjOTIwZC1kNGEwLTQ5YzctYWU1My04MmJlMWQ1NzczNzAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MTJUMTIyMzQ5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZjFlYWUyMjUwYzFiMzMxZGQ5YjllYjUwZDk4ZjQ2Zjc2NTQ0Zjk2MmVjNmU0NDRiZGQ3NWRkODc4YWRiOGVmYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.sOi55E1-pLCmckLgThbFRRDyxeLRnrqLV-qw1vc_vTA)
GNU Radio was installed from the main repository, following Installing instructions in GNU Radio website for Ubuntu 22.04.
I've cloned from the branch maint-3.10 as I saw you pointed out in some other answer to work with GNU Radio 3.10:
$ git clone https://github.com/bastibl/gr-ieee802-11 --branch maint-3.10
Also python is able to correctly import module (I use asdf as version manager):
I've already checked issue #268, #208, #192 but none was enough. Somehow python inside GNU Radio is not able to find ieee802_11 module, even after specifying
PYTHONPATH
andLD_LIBRARY_PATH
as I saw in other issues.Considering what you've pointed out in previous answers:
Is it possible to have some differences between
main
undmaint-3.10
branches that could cause problems?Or perhaps I'm still missing something?
Thank you.
The text was updated successfully, but these errors were encountered: