Arch Linux

caelia

Member

Registered: 2016-05-14

Posts: 15

[SOLVED] Package build errors

Sorry about the vague title. Not sure what else to call this post ...

Anyway, I've been trying to install some network recon tools from Project Discovery, and I keep getting the following error:

cc1: error: '-fstack-check=' and '-fstack-clash-protection' are mutually exclusive; disabling '-fstack-check=' [-Werror]
cc1: all warnings being treated as errors
==> ERROR: A failure occurred in build().
    Aborting...

I build packages from the AUR pretty often, and I have seen this a few times before, but mostly those packages were just things I wanted to play around with. These are fairly important to me.

I've observed that this ...

cc1: error: '-fstack-check=' and '-fstack-clash-protection' are mutually exclusive; disabling '-fstack-check=' 

... is quite common as a warning. Much less common for compilation to abort due to -Werror.

The most obvious solution is to override -Werror. But I'm not sure how to do that. Given that there is a whole family of related tools which appear to come from the same team and use the same build process (? not totally sure about that last, but at least they're all written in Go), and that other people have built these packages and are not reporting the same error, it seems as though there must be some setting on my system that is causing this to happen, but I have no idea what that might be ...

I have tried the following to override the -Werror flag:

$ CFLAGS+=" -Wno-error"

And I have tried editing makepkg.conf to read:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Wno-error \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"

Neither of these measures has made any difference. I have compared my installed /etc/makepkg.conf against the one from the current pacman package; the only change is the edit noted above.

I've also checked the Makefile from a couple of these packages, and -Werror is not set there. So where is this flag coming from, and how can I disable it?

Last edited by caelia (Today 13:17:58)

mackin_cheese

Member

Registered: 2025-01-07

Posts: 380

Re: [SOLVED] Package build errors

Please post the command you were using to install the package along with the full output.

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

Please post the command you were using to install the package along with the full output.

Not sure how this helps, but OK ... first of all, I haven't gotten to installing the package(s) since I can't get them to compile. But anyway, the command is just

$ makepkg

Except for the couple of times I tried

$ CFLAGS+=' -Wno-error' makepkg

And the full output for the package I was trying to build today (tlsx) is just the following:

==> Making package: tlsx 1.1.9-1 (Sat 05 Apr 2025 09:04:12 PM MDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found tlsx-1.1.9.tar.gz
==> Validating source files with sha256sums...
    tlsx-1.1.9.tar.gz ... Passed
==> Extracting sources...
  -> Extracting tlsx-1.1.9.tar.gz with bsdtar
==> Starting prepare()...
==> Starting build()...
# runtime/cgo
cc1: error: '-fstack-check=' and '-fstack-clash-protection' are mutually exclusive; disabling '-fstack-check=' [-Werror]
cc1: all warnings being treated as errors
==> ERROR: A failure occurred in build().
    Aborting...

I've attempted to build a couple of other related packages, with many more lines of compiler output, but in each case the fatal error is the same.

And is it not obvious that the error is caused by the fstack-check - fstack-clash-protection conflict, with -Werror being enabled somehow (and I can't figure out how)? Or do you suspect that there is some non-obvious meaning to that seemingly clear error message?

mackin_cheese

Member

Registered: 2025-01-07

Posts: 380

Re: [SOLVED] Package build errors

okay two things.

1. Perform a full system update, then reboot, then try making the package.
2. If that fails, build the package in a clean CHROOT

I was able to build the package

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

I've attempted to build a couple of other related packages, with many more lines of compiler output, but in each case the fatal error is the same.

Actually, no, there aren't more lines of compiler output. I just made another attempt to build httpx, which is a more commonly used tool from the same team, and in this case there are many Go language dependencies that need to be downloaded. So the "many more lines" are messages about downloading dependencies. Just as with tlsx, the build is aborted before any actual compilation steps take place.

mackin_cheese

Member

Registered: 2025-01-07

Posts: 380

Re: [SOLVED] Package build errors

Okay let's try doing what i suggested and see if that helps

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

okay two things.

1. Perform a full system update, then reboot, then try making the package.

OK. I have updated and rebooted at least once between the first time this happened and today, but I'm a good sport, so I'll try it - 99.9% sure it won't help.

2. If that fails, build the package in a clean CHROOT

You mean, as described on this wiki page? https://wiki.archlinux.org/title/Develo … ean_chroot

I was able to build the package

... as have other people, which is why I think there must be some odd setting buried somewhere on my system.

mackin_cheese

Member

Registered: 2025-01-07

Posts: 380

Re: [SOLVED] Package build errors

yes as described in teh wiki page

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

yes as described in teh wiki page

OK. As expected, updating my system and rebooting made no difference.

The package compiled without errors in a clean chroot. So, what does that tell us?

Last edited by caelia (Today 11:59:02)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,553

Re: [SOLVED] Package build errors

Do you have $XDG_CONFIG_HOME/pacman/makepkg.conf or ~/.makepkg.conf? What's the output of `env`?

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

Do you have $XDG_CONFIG_HOME/pacman/makepkg.conf or ~/.makepkg.conf?

No, don't have either of those.

What's the output of `env`?

I thought of that, and checked for any relevant variables; I don't see anything, but in case I've missed something:

$ env |sort 
CAELIAS_XINITRC=yes
CASROOT=/usr
CHICKEN_INSTALL_REPOSITORY=/usr/local/lib/chicken/11/
CHICKEN_REPOSITORY_PATH=/usr/local/lib/chicken/11/:/usr/lib/chicken/11/
COLORTERM=truecolor
CSF_DrawPluginDefaults=/usr/share/opencascade/resources/DrawResources
CSF_EXCEPTION_PROMPT=1
CSF_IGESDefaults=/usr/share/opencascade/resources/XSTEPResource
CSF_LANGUAGE=us
CSF_MDTVTexturesDirectory=/usr/share/opencascade/resources/Textures
CSF_MIGRATION_TYPES=/usr/share/opencascade/resources/StdResource/MigrationSheet.txt
CSF_OCCTResourcePath=/usr/share/opencascade/resources
CSF_PluginDefaults=/usr/share/opencascade/resources/StdResource
CSF_SHMessage=/usr/share/opencascade/resources/SHMessage
CSF_STEPDefaults=/usr/share/opencascade/resources/XSTEPResource
CSF_ShadersDirectory=/usr/share/opencascade/resources/Shaders
CSF_StandardDefaults=/usr/share/opencascade/resources/StdResource
CSF_StandardLiteDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjDefaults=/usr/share/opencascade/resources/StdResource
CSF_TObjMessage=/usr/share/opencascade/resources/TObj
CSF_XCAFDefaults=/usr/share/opencascade/resources/StdResource
CSF_XSMessage=/usr/share/opencascade/resources/XSMessage
CSF_XmlOcafResource=/usr/share/opencascade/resources/XmlOcafResource
CSSTRNGS=/usr/share/locale
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
DESKTOP_SESSION=xfce
DISPLAY=:0.0
DRAWDEFAULT=/usr/share/opencascade/resources/DrawResources/DrawDefault
DRAWHOME=/usr/share/opencascade/resources/DrawResources
EDITOR=helix
FLUTTER_HOME=/opt/flutter
GIT_EDITOR=helix
GLFW_IM_MODULE=ibus
GRADLE_HOME=/usr/share/java/gradle
GTK_IM_MODULE=fcitx
GTK_MODULES=canberra-gtk-module
HAXE_STD_PATH=/usr/share/haxe/std
HG=/usr/bin/hg
HOME=/home/caelia
ISE_EIFFEL=/opt/estudio
ISE_PLATFORM=linux-x86-64
KITTY_INSTALLATION_DIR=/usr/lib/kitty
KITTY_PID=1535
KITTY_PUBLIC_KEY=1:=qA`Fd}lKG9(`LS^9iM~Dad@uSwt!mny1vczRG84
KITTY_WINDOW_ID=3
LANG=en_US.UTF-8
LC_COLLATE=C
LOGNAME=caelia
MAIL=/var/spool/mail/caelia
MMGT_CLEAR=1
MOTD_SHOWN=pam
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins
OLDPWD=/s/v0/grooby/smj
OPCODE6DIR=/usr/lib/csound/plugins64-6.0
OSFONTDIR=/usr/local/share/fonts/otf:/usr/local/share/fonts/ttf
PANEL_GDK_CORE_DEVICE_EVENTS=0
PATH=/home/caelia/bin:/home/caelia/.cargo/bin:/usr/lib/hardening-wrapper/bin:/usr/local/bin:/usr/bin:/opt/estudio/studio/spec/linux-x86-64/bin:/opt/flutter/bin:/usr/lib/plan9/bin
PLAN9=/usr/lib/plan9
PWD=/home/caelia
QT_IM_MODULE=fcitx
RAWWAVE_PATH=/usr/share/stk/rawwaves
SESSION_MANAGER=local/nessie:@/tmp/.ICE-unix/1020,unix/nessie:/tmp/.ICE-unix/1020
SHELL=/bin/zsh
SHLVL=4
SSH_AGENT_PID=977
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXNu450G/agent.976
STARSHIP_SESSION_KEY=1974422361319071
STARSHIP_SHELL=zsh
TERM=xterm-256color
TERMINFO=/usr/lib/kitty/terminfo
USER=caelia
WINDOWID=50331662
WINDOWPATH=1
XAUTHORITY=/home/caelia/.Xauthority
XDG_CACHE_HOME=/home/caelia/.cache
XDG_CONFIG_DIRS=/etc/xdg
XDG_CONFIG_HOME=/home/caelia/.config
XDG_CURRENT_DESKTOP=XFCE
XDG_DATA_DIRS=/usr/local/share:/usr/share
XDG_MENU_PREFIX=xfce-
XDG_RUNTIME_DIR=/run/user/1002
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_ID=1
XDG_SESSION_TYPE=tty
XDG_VTNR=1
XMODIFIERS=@im=fcitx
X_PROFILE=
_=/usr/bin/env

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,553

Re: [SOLVED] Package build errors

I'll bet it's that /usr/lib/hardening-wrapper/bin in PATH.

caelia

Member

Registered: 2016-05-14

Posts: 15

Re: [SOLVED] Package build errors

I'll bet it's that /usr/lib/hardening-wrapper/bin in PATH.

Haha! Yes. That caught my eye, too. And indeed, it appears that was the problem. Looks like I installed the [no longer extant] hardening-wrapper package as a build dep for an AUR package that I installed 8 years ago; I've never had any other use for it.

Thank you very much!