https://sourceware.org/bugzilla/show_bug.cgi?id=33078

            Bug ID: 33078
           Summary: strip misbehaves on non-LTO static libraries
           Product: binutils
           Version: 2.45 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: sam at gentoo dot org
                CC: hjl.tools at gmail dot com
  Target Milestone: ---

strip on trunk doesn't seem to handle regular static libraries (note that 2.44
below is with the relevant patches from trunk applied, so compare it to 2.43):
```
$ ./test.sh
+ rm '*.a' a.o foo.a.bak foo.a.stripped.2.43 foo.a.stripped.2.44
foo.a.stripped.9999
rm: cannot remove '*.a': No such file or directory
+ cat
+ gcc a.c -o a.o -c -ggdb3
+ ar q foo.a a.o
ar: creating foo.a
+ cp foo.a foo.a.bak
+ for ver in 9999 2.44 2.43
+ strip_with_ver 9999 foo.a
+ local strip_ver=9999
+ local target=foo.a
+ cp foo.a.bak foo.a
+ /usr/x86_64-pc-linux-gnu/binutils-bin/9999/strip -d -v foo.a
copy from `foo.a(a.o)' [unknown] to `stoFmyjx/a.o' [unknown]
+ mv foo.a foo.a.stripped.9999
+ for ver in 9999 2.44 2.43
+ strip_with_ver 2.44 foo.a
+ local strip_ver=2.44
+ local target=foo.a
+ cp foo.a.bak foo.a
+ /usr/x86_64-pc-linux-gnu/binutils-bin/2.44/strip -d -v foo.a
copy from `foo.a(a.o)' [unknown] to `st3YDfe5/a.o' [unknown]
+ mv foo.a foo.a.stripped.2.44
+ for ver in 9999 2.44 2.43
+ strip_with_ver 2.43 foo.a
+ local strip_ver=2.43
+ local target=foo.a
+ cp foo.a.bak foo.a
+ /usr/x86_64-pc-linux-gnu/binutils-bin/2.43/strip -d -v foo.a
copy from `foo.a(a.o)' [elf64-x86-64] to `st7xxA9I/a.o' [elf64-x86-64]
+ mv foo.a foo.a.stripped.2.43
+ ls -hal foo.a.bak foo.a.stripped.2.43 foo.a.stripped.2.44 foo.a.stripped.9999
-rw-r--r-- 1 sam sam  18K Jun 11 18:51 foo.a.bak
-rw-r--r-- 1 sam sam 1.7K Jun 11 18:51 foo.a.stripped.2.43
-rw-r--r-- 1 sam sam  18K Jun 11 18:51 foo.a.stripped.2.44
-rw-r--r-- 1 sam sam  18K Jun 11 18:51 foo.a.stripped.9999
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to