-
Notifications
You must be signed in to change notification settings - Fork 87
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
Compilation error on GCC 10 due to multiple definitions of __packed #32
Comments
removing `__packed' from radiotap/radiotap.h fixed it. patch:
|
This happened for me when installing from AUR, and this patch fixes it. Thanks! My system is on gcc 10.1.0. |
This was a problem with |
Closed
schmittner
added a commit
that referenced
this issue
Jun 22, 2020
bjzhang
added a commit
to bjzhang/xuxiake
that referenced
this issue
Oct 27, 2022
``` -} __packed; +} __attribute__((__packed__)); ``` reference: seemoo-lab/owl#32 (comment) Signed-off-by: Bamvor ZHANG <bamv2005@gmail.com>
bjzhang
added a commit
to bjzhang/xuxiake
that referenced
this issue
Oct 30, 2022
1. Add system system register wrapper function; 2. Add mmu code for aarch64; 2.1 Add mmu enable function; 2.2 Add L0 and L1 page table to support 1G size page mapping; 2.3 Set proper access permission; 3. Add CONFIG_USERSPACE and CONFIG_MMU for building. One could build with userspace or mmu supporting with the following line `make CFLAGS="-DCONFIG_USERSPACE"`` `make CFLAGS="-DCONFIG_MMU"`` 4. Note that previous commit make use of wrong method for pack. It should be ` __attribute__((__packed__))` instead of `__packed`. Reference the following link for more information seemoo-lab/owl#32 (comment) Signed-off-by: Bamvor ZHANG <bamv2005@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting from the upcoming GCC release 10, the default of
-fcommon
option will change to-fno-common
- this leads to build errors:See also:
sahlberg/libiscsi#308
https://bugzilla.suse.com/show_bug.cgi?id=1160276
https://bugzilla.suse.com/show_bug.cgi?id=1160244
The text was updated successfully, but these errors were encountered: