Arch Linux User Repository

@lquidfire Apparently I haven't mentioned it here before even though I referenced my makepkg.conf I use but in fact I already do that (and yes, I could improve that script a bit).
That's why I couldn't reproduce the issues people commented here so far and discarded their messages as using a probably outdated makepkg.conf or some other system configuration polluting their build environments.

The package builds in a clean chroot0, and also on my system.

Could you please share your config.log?

@SunRed: If I may make the suggestion: Since you share this PKGBUILD on the AUR (not just for your personal use), it would be recommended to always test in a clean chroot.

Package fails to build with default makepkg.conf. Still the fortify_source error.

I think this package does need updated per arzeth's comment, I have the following flags and options in makepkg conf - which I think is default, I can't recall editing it - and it fails with the same fortify_source error:

#CPPFLAGS=""
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
         -Wl,-z,pack-relative-relocs"
LTOFLAGS="-flto=auto"
RUSTFLAGS="-Cforce-frame-pointers=yes"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"
DEBUG_RUSTFLAGS="-C debuginfo=2"

BUILDENV=(!distcc color !ccache check !sign)
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

Although for reasons I don't really understand this results in this output:

==> Starting build()...
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt"

@arzeth Sorry I didn't see your comment earlier. I myself test the packages with a rather highly optimized makepkg.conf due to which I may not have encountered this problem but -O2 should already be present in the default one on Arch.

I had to add

export CPPFLAGS="${CPPFLAGS} -O2"

after the cd line

because otherwise

/usr/include/features.h:414:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
  414 | #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
      |    ^~~~~~~
configure: error: (E) rcd_autogen failed

even though I have -Ofast in CFLAGS and CXXFLAGS in /etc/makepkg.conf

Please update:

pkgver=0.0.31

md5sums=('c754a158f568b4bf0de6802fbf6f652a')

Works perfectly fine for me.

Thanks.

Version 0.0.31 works just fine with whatever wxwidgets is current

A workaround in the meantime without downgrading is to use some fresh user account, no gtk theme set, no specific fonts, etc... This works, even though it may have a small chance of segfaulting at launch, just retry.

@Strykar Following the comment of @net147 downgraded wxwidgets-gtk3 to version 3.2.2.1. Working for now.