Although only a static file is shown, results are the same for dynamic objects. Having selected sstrip: mszick@deb2core:/Builds/BLDRT/buildroot$ ls -l output/target/sbin/pkgdetails -rwxr-xr-x 1 mszick mszick 42199 2009-11-18 12:41 output/target/sbin/pkgdetails mszick@deb2core:/Builds/BLDRT/buildroot$ file output/target/sbin/pkgdetails output/target/sbin/pkgdetails: ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), statically linked, corrupted section header size Having selected strip: mszick@deb2core:/Builds/BLDRT/buildroot/output/target/sbin$ ls -l pkgdetails -rwxr-xr-x 1 mszick mszick 46992 2009-11-18 13:38 pkgdetails mszick@deb2core:/Builds/BLDRT/buildroot/output/target/sbin$ file pkgdetails pkgdetails: ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), statically linked, with unknown capability 0xf41 = 0x756e6700, stripped
Does the resulting file runs properly on the target or not ? I'm not sure what sstrip does compared to strip, but it might be that sstrip strips things that confuse tools such as "file" while still allowing the program to run properly.
Quite likely fixed by http://git.buildroot.net/buildroot/commit/?id=c0e307b848d8de23e6f10a179c4f240c023c8b82