This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: updated question : Three questions when building newlib with arm-none-eabi toolchain


On 03/30/2011 06:28 AM, Can Finner wrote:
Hi, I previously sent this message but got no suggestion. in the past
days I got a little progress and try to present the question again
now.

in file ./libgloss/config/default.mh, it says that the multilib option
is passed in $(CFLAGS).

targets like m68k seem to use
$(CC) $(CFLAGS_FOR_TARGET) $(CFLAGS) $(INCLUDES)
<target-specific-defines>  -o $@ -c
to compile target libraries and crt0s.

the problem is that the counterpart Makefile rules in arm target as
following does not use $(CFLAGS).
$(CC) $(CFLAGS_FOR_TARGET) $(INCLUDES) -DARM_RDI_MONITOR -o $@ -c  $<

This results in target libraries like librdimon.a are built without
multilib option, which are useless.

So any tips? Thanks.


Can,


Sorry for letting this slip.

It would appear that $(CFLAGS) was omitted in each of the commands in libgloss/arm/Makefile.in as you have noted. It is being passed as part of the multi-lib processing in the top-level libgloss directory.

I have attached the patch.

-- Jeff J.

Attachment: arm-makefile-in.patch
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]