Should strip gnore the unknown files in archive?

[Mike Frysinger]

On Tuesday 07 June 2005 10:19 pm, Alan Modra wrote:
> On Tue, Jun 07, 2005 at 04:31:36PM -0700, H. J. Lu wrote:
> > When strip is used on an archive with mixed .o and .c files, it will
> > report an error:
> >
> > http://sources.redhat.com/bugzilla/show_bug.cgi?id=995
> >
> > Should strip gnore the unknown files in archive?
>
> Do you think "strip foo.c" should warn?  If so, then strip on unknown
> files in archives should warn too.  I suppose it would be nice for strip
> to continue processing other files in the archive, which doesn't seem to
> be the case now.

slightly offtopic ... but it seems like strip doesnt clean up after itself 
properly when running on unknown objects ...

$ file a.out 
a.out: ELF 32-bit MSB executable, Motorola 68020, version 1 (SYSV), for 
GNU/Linux 2.4.1, dynamically linked (uses shared libs), not stripped
$ strace -f -eopen strip a.out 2>&1 | grep -v O_RDONLY
open("st3UTwVL", O_RDWR|O_CREAT|O_TRUNC, 0666) = 4
strip: Unable to recognise the format of the input file a.out
$ file st3UTwVL
st3UTwVL: empty
-mike