-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
vagrant: add Vagrantfile to test native in FreeBSD #14458
Conversation
d0d356e
to
8dd2f6f
Compare
Rebased and squashed to current master. |
When trying to run the network test indicated in the README I get the following:
|
I pointed that out in OP though:
|
Ok, but then why is that particular example used in the README, knowing that it will not work? |
Because I am stupid 😅 I used the first example found, not checking if it uses |
Actually the applications start, but communication does not work. Just another thing to figure out ;-). I reworded it now to refer to |
Please squash @miri64 ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I followed the instructions and got it working, also @miri64 has provided test output. Some follow-up work is needed but I see no reason not to merge this. ACK.
35c5361
to
9a291ab
Compare
Squashed and added whitelisting to the build system sanity check. |
Vagrantfiles are not part of our build-system so they should be ignored by its sanity check.
9a291ab
to
1d435de
Compare
Contribution description
This provides a Vagrantfile for testing RIOT
native
in FreeBSD.Testing procedure
Basically, follow the provided README.md. For the
tapsetup
stuff to work #14457 is required.I also ran
dist/tools/compile_and_run_for_board
on it overnight, the results can be found here.Basically there are some errors (but this does not block this PR), that can be summarized as such:
ports
, maybe another argument for native: 64-Bit support? #6603)sha512sum
orbridge
and other missing toolingpthread
sscapy
sublayerAll fixes that can be tackled as follow-ups (I will open a tracking issue if desired).
Issues/PRs references
None