Re: All packages that use Meson are built with -O0

[Jonathan Schleifer <js%NetBSD.org@localhost>]

Am 11.08.24 um 20:06 schrieb Thomas Klausner:

> I asked you to check your work/.work.log. Can you please do that?

The initial message already quoted the glibc warning, which should have 
been obvious enough in that it's definitely -O0, but here you go:

niflheim objpgsql> grep O0 work/.work.log
[*] cc -L/opt/pkg/lib -L/usr/lib64 -I/opt/pkg/include -I/usr/include 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp418hamts/testfile.m 
-o 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp418hamts/output.exe 
-D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Wl,-zrelro -Wl,-R/opt/pkg/lib -Wl,-R/usr/lib64
<.> /opt/pkg/bin/clang -fcommon -Qunused-arguments 
-Wno-error=implicit-int -Wno-error=int-conversion 
-Wno-error=incompatible-pointer-types -m64 -fstack-protector-strong 
-D_FORTIFY_SOURCE=2 -Wl,-zrelro 
-L/home/js/Devel/pkgsrc/databases/objpgsql/work/.buildlink/lib 
-I/home/js/Devel/pkgsrc/databases/objpgsql/work/.buildlink/include 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp418hamts/testfile.m 
-o 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp418hamts/output.exe 
-D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Wl,-zrelro -Wl,-rpath,/opt/pkg/lib -Qunused-arguments
[*] cc -I/opt/pkg/include -I/usr/include 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp7vpcyk4d/testfile.m 
-o 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp7vpcyk4d/output.obj 
-c -D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Werror=unknown-warning-option -Werror=unused-command-line-argument 
-Werror=ignored-optimization-argument --print-search-dirs
<.> /opt/pkg/bin/clang -fcommon -Qunused-arguments 
-Wno-error=implicit-int -Wno-error=int-conversion 
-Wno-error=incompatible-pointer-types -m64 -fstack-protector-strong 
-D_FORTIFY_SOURCE=2 -Wl,-zrelro 
-I/home/js/Devel/pkgsrc/databases/objpgsql/work/.buildlink/include 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp7vpcyk4d/testfile.m 
-o 
/home/js/Devel/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp7vpcyk4d/output.obj 
-c -D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Werror=unknown-warning-option -Werror=unused-command-line-argument 
-Werror=ignored-optimization-argument --print-search-dirs -Qunused-arguments

I mean. It's documented behavior in Meson, so not surprising. And before 
you ask:

niflheim ~> grep CWRAPPERS /opt/pkg/etc/mk.conf
niflheim ~>

So no change there.

And just in case, here's the same on a NetBSD machine:

[*] cc -L/usr/pkg/lib -L/usr/lib -I/usr/pkg/include -I/usr/include 
-I/usr/include/krb5 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp_xk4gf3x/testfile.m 
-o 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp_xk4gf3x/output.exe 
-D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Wl,-zrelro -Wl,-R/usr/pkg/lib -Wl,-R/usr/lib
<.> /usr/pkg/bin/clang -fcommon -Qunused-arguments 
-Wno-error=implicit-int -Wno-error=int-conversion 
-Wno-error=incompatible-pointer-types -fstack-protector-strong 
-D_FORTIFY_SOURCE=2 -Wl,-zrelro -fPIC 
-L/usr/pkgsrc/databases/objpgsql/work/.buildlink/lib 
-I/usr/pkgsrc/databases/objpgsql/work/.buildlink/include 
-I/usr/include/krb5 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp_xk4gf3x/testfile.m 
-o 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmp_xk4gf3x/output.exe 
-D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Wl,-zrelro -Wl,-rpath,/usr/pkg/lib -Qunused-arguments -pie
[*] cc -I/usr/pkg/include -I/usr/include -I/usr/include/krb5 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmpmcyg67k6/testfile.m 
-o 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmpmcyg67k6/output.obj 
-c -D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Werror=unknown-warning-option -Werror=unused-command-line-argument 
-Werror=ignored-optimization-argument --print-search-dirs
<.> /usr/pkg/bin/clang -fcommon -Qunused-arguments 
-Wno-error=implicit-int -Wno-error=int-conversion 
-Wno-error=incompatible-pointer-types -fstack-protector-strong 
-D_FORTIFY_SOURCE=2 -Wl,-zrelro -fPIC 
-I/usr/pkgsrc/databases/objpgsql/work/.buildlink/include 
-I/usr/include/krb5 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmpmcyg67k6/testfile.m 
-o 
/usr/pkgsrc/databases/objpgsql/work/objpgsql-1.0/output/meson-private/tmpmcyg67k6/output.obj 
-c -D_FILE_OFFSET_BITS=64 -O0 -Werror=implicit-function-declaration 
-Werror=unknown-warning-option -Werror=unused-command-line-argument 
-Werror=ignored-optimization-argument --print-search-dirs -Qunused-arguments

And also CWRAPPERS:

nil objpgsql> grep CWRAPPERS /etc/mk.conf
nil objpgsql>

> Just because what the build system prints contains -O0 does not mean
> that it is compiled with -O0 because the cwrappers change the actual
> flags passed to the compiler.

glibc complaining that _FORTIFY_SOURCE cannot be used without -O should 
be a dead giveaway that -O0 is what's actually being used during 
compilation (this is how I even noticed).

--
Jonathan