mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6115] build: cannot compile with landlock disabled on Ubuntu 16.04 (gcc 9.5.0) #3188
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Dec 5, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6115
Building firejail from git master fails on ubuntu with kernel 4.15.0-220-generic (regardless of using
--enable-landlockor not).Here's the relevant output:
@netblue30 Can you have a look please?
@kmk3 commented on GitHub (Dec 5, 2023):
I added this code, I'll look into it.
What is the version of Ubuntu, gcc and glibc used?
What is the output of the following commands?
Relates to #6078.
@ghost commented on GitHub (Dec 5, 2023):
This is Ubuntu 16.04.07 LTS with Expanded Security Maintenance (ESM).
@kmk3 commented on GitHub (Dec 5, 2023):
Strange, that gcc version is not that old to be having issues with this.
Did you manually enable
-Wpedanticand-Werror?Is this in a VM or CI?
Please post the full build log of ./configure and make.
@ghost commented on GitHub (Dec 5, 2023):
Nope, I build firejail from git on Ubuntu just like I do on my Arch Linux setup. Dual-booting both Linuxes; so bare metal, no VM or CI involved.
Here you go:
./configure log: https://x0.at/eiLY.w8LKzE8
make log: https://x0.at/SQ6V.tolJoZH
@kmk3 commented on GitHub (Dec 7, 2023):
Does the following work?
What is the output of this:
@ghost commented on GitHub (Dec 7, 2023):
No changes, getting the same errors:
https://x0.at/BacG.Y5iD3Za
https://x0.at/hp-z.Iiz2yjp
@kmk3 commented on GitHub (Dec 7, 2023):
Alright, I managed to make gcc print warnings:
I was forgetting to use
--disable-landlockto make it compile the lines inquestion.
I think I'll just remove them for now and maybe try a more portable version
later.
@kmk3 commented on GitHub (Dec 7, 2023):
What does the following show?
Also, could you post the output directly so that the details are centralized
and available for future reference?
It can be just the relevant make lines (as in my previous comment) so that it
doesn't exceed the character limit.
@ghost commented on GitHub (Dec 7, 2023):
@kmk3 commented on GitHub (Dec 8, 2023):
So even when the compiler flags are the same it causes an error.
I suppose that basic support for that was indeed added rather recently to gcc
then.
It seems a bit surprising that it only warns with
-Wpedanticin recentversions (rather than requiring something like
-std=gnu99), as it is onlypart of C23 (which has not been published yet) and is not in older versions of
gcc.
Note: I have a WIP branch that adds
-std=c99 -Wpedanticto CFLAGS in CI,which will hopefully catch similar issues.
@ghost commented on GitHub (Dec 8, 2023):
@kmk3 Thanks for all the work, builds fine again now!