Bug #219

binutils: strip does not set the executable bit

Added by Natanael Copa about 2 years ago. Updated about 1 year ago.

Status:Closed Start date:12/14/2009
Priority:Low Due date:
Assignee:- % Done:

0%
Category:-
Target version:-

Description

strip /bin/busybox -o walrus
ls -l walrus 
-rw-r--r-- 1 ncopa ncopa 773272 Dec 14 08:37 walrus

From: http://lists.impactlinux.com/pipermail/firmware-impactlinux.com/2009-December/000529.html

It removed the executable bit from the file. I take it this is a gcc 4.4 bug?
(Ahem, not a bug, a "random new unannounced behavior change".)

http://www.opengroup.org/onlinepubs/9699919799/utilities/strip.html

The effect of strip on object and executable files shall be similar to the use
of the -s option to c99

http://www.opengroup.org/onlinepubs/9699919799/utilities/c99.html

The executable file shall be created as specified in File Read, Write, and
Creation, except that the file permission bits shall be set to: S_IRWXO |
S_IRWXG | S_IRWXU

So yeah, it looks like gcc 4.4 is in violation of susv4 by not setting the
executable bit on its output files.

History

#1
Updated by Natanael Copa about 2 years ago

  • Priority changed from Normal to Low

not sure how much we really care about this

#2
Updated by Natanael Copa about 1 year ago

  • Status changed from New to Closed

closing

Also available in: Atom PDF