Closed jmaibaum closed 6 years ago
Those are from assert (3)
, define -DNDEBUG and they'll go away.
make OPTIMIZATIONS="-O3 -ffast-math -fomit-frame-pointer -fno-finite-math-only -DNDEBUG"
or if your distro is OK with shipping x86 binaries that support SSE2 or later
make OPTIMIZATIONS="-msse -msse2 -mfpmath=sse -O3 -ffast-math -fomit-frame-pointer -fno-finite-math-only -DNDEBUG"
Hi @x42 ,
while updating the AUR build definitions for setBfree v0.8.7 I have noticed the following output during the package build process (re-testing the previous version v0.8.5 showed that this is not a new issue, it has been there before):
grep
ing the installed files from the package with the absolute src path used during build indeed shows these matches:These matches don't seem to be vital, as running
grep
on the hexdump only reveals what seem to be mere references to the source files, i.e. it's most probably only debugging info (the other two files have similar matches):From a quick glance I found an
abspath
command in: https://github.com/pantherb/setBfree/blob/ff15bf2fdb85120c5125deb5debdcabb3969c6a4/Makefile#L13While deleting the build directory does no harm (i.e. you can still run the apps and the plugin GUI without crashes), as it is to be expected if they are only debugging info, I still wanted to know if/how it would be possible to suppress the adding of the absolute build path to the linked executables and libraries. Users who build this package from the AUR will see those messages and might be thinking that this is a packaging bug.
FYI, the files were already
strip
ped during build (at least stripping them manually after the build has finished doesn't change anything).