NetworkManager built with pmbootstrap: no dynamic symbols defined
Created by: ollieparanoid
I don't understand why when I build networkmanager using pmOS I get no dynamic symbols defined in the NetworkManager binary while the package from alpine has dynamic symbols defined in the binary. the symbols are needed for the plugin .so files that are loaded from the binary. If you have any hints what compiler/linker/... flags could cause this I would already be really happy. I could reproduce that issue both on x86_64 and on armhf. I checked a very recently (yesterday?) built alpine package on x86 and it is definitely okay so I am pretty sure it is not a recent change in alpine. the thing is: not even the binary in the "src" directory has the symbols. so it must be something in the compiler/linker. Julian Goldsmith: I have copied the alpine package to pmos and I am building it using pmbootstrap build I need a version with dhclient support and even though alpine has merged a change that adds dhclient support now, it hasn't been built for armhf yet. and I think even if the binary package from alpine would solve the issue, it would still be good to find out the underlying issue as it might happen with other packages, too.
Yeah, I'd think it would be built the same between pmOS and Alpine, if the APKBUILD is the same I'd see if you can get ahold of the CFLAGS pmbootstrap is using when it runs abuild
I think that too, but I have this problem both with the old and the new apkbuild which I copied using "cp -r" from the alpine aports. according to /etc/abuild.conf in the chroot it should be "-Os -fomit-frame-pointer" since when are release builds built with "-Os"? hm, config.log tells me the following: CFLAGS=' -fdata-sections -ffunction-sections -Wl,--gc-sections -Os -fomit-frame-pointer -fno-strict-aliasing'