Martin Husemann wrote: > How about: remove all *.a files from those images? > Is there a tool to strip CTF from binaries?
I really don't like the general idea of introducing differences between images and systems installed through sysinst. It's confusing for users, and also means that testing of one is less likely to apply to the other. I see that libstdc++_pic.a is much larger than the other versions of the same library: # cd /usr/lib # ls -al libstdc* -r--r--r-- 1 root wheel 4539634 Aug 8 14:00 libstdc++.a lrwxr-xr-x 1 root wheel 16 Aug 8 14:00 libstdc++.so -> libstdc++.so.9.0 lrwxr-xr-x 1 root wheel 16 Aug 8 14:00 libstdc++.so.9 -> libstdc++.so.9.0 -r--r--r-- 1 root wheel 2030136 Aug 8 14:00 libstdc++.so.9.0 -r--r--r-- 1 root wheel 4787754 Aug 8 14:00 libstdc++_p.a -r--r--r-- 1 root wheel 28835160 Aug 8 14:00 libstdc++_pic.a and that it contains .debug_info sections, which the others don't: # size -A -d libstdc++_pic.a | fgrep .debug_info | wc -l 173 # size -A -d libstdc++.a | fgrep .debug_info | wc -l 0 Other libraries also have _pic.a files that are much larger than the others versions. Is there a bug that causes them not to be CTF-converted, or is this deliberate? -- Andreas Gustafsson, g...@netbsd.org