This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
bfd + chew + execute
- From: NightStrike <nightstrike at gmail dot com>
- To: binutils <binutils at sourceware dot org>
- Date: Fri, 12 Apr 2013 08:50:33 -1000
- Subject: bfd + chew + execute
For gcc on windows, gcc won't set the execute bit if the file
extension is not .exe. bfd does some things while building where it
creates a program called chew... but it does this: gcc -o chew.&&;
../../move-if-change chew.$$ chew.exe
So under certain cross compiler conditions, chew is left in a
non-executable state, whereas gcc -o chew.exe works fine. Is it
really necessary to mess with the file extension here? Can we do
something like this?
- $(CC_FOR_BUILD) -o chew.$$$$ $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) \
+ $(CC_FOR_BUILD) -o chew$$$$$(EXEEXT_FOR_BUILD)
$(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) \
and:
- $(SHELL) $(srcdir)/../../move-if-change chew.$$$$ $(MKDOC)
+ $(SHELL) $(srcdir)/../../move-if-change
chew$$$$$(EXEEXT_FOR_BUILD) $(MKDOC)
?