mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3075] configure script breaks #1929
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#1929
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 @matu3ba on GitHub (Dec 8, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3075
Upon running
./configurecommitacd14b8f4fbroke master withhecking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
./configure: line 3076: syntax error near unexpected token
newline' ./configure: line 3076:AX_CHECK_COMPILE_FLAG('Can anybody else reproduce?
Line 3021 looks edgy, but it might be easier to recreate the automake output.
@ghost commented on GitHub (Dec 8, 2019):
@matu3ba I commented with the same issue in
acd14b8f4f. Until there's a proper fix you can unbreak git master by runningautoreconf -vfiprior to configure.@netblue30 commented on GitHub (Dec 9, 2019):
Thanks @glitsj16, @matu3ba. I've seen the comment. I have no idea what's going on. The script was generated on a Debian stable. I've seen the problem a few months ago, then it disappeared. To fix it locally I used to run"autoreconf -i --install".
I generated a new configure script on Debian 8 and checked it in (
8c4a8801e4)@Fred-Barclay commented on GitHub (Dec 9, 2019):
Just checked on Arch, all good now. 😄
@matu3ba commented on GitHub (Dec 9, 2019):
Thanks @netblue30 for the fast fix. On Manjaro it works for me now. I would suggest to close this bug after the proper fix was tested.
@ghost commented on GitHub (Dec 14, 2019):
Fixed via
8c4a8801e4, closing.