-mfloat-abi=softfp

ng@piments.com ng@piments.com
Mon Apr 19 01:22:00 GMT 2010


On 04/18/10 20:58, Martin Guy wrote:
> On 4/18/10, ng@piments.com<ng@piments.com>  wrote:
>>   I am experimenting with building a toolchain with maverick enabled based on
>> patching gcc according to Martin Guy's patch set.
>> http://martinwguy.co.uk/martin/crunch/
>>
>>   He suggests using -mfpu=maverick -mfloat-abi=softfp
>>
>>   I am having difficulty locating this in ct-ng menuconfig. There is HW or SW
>> option but help does not say what switches this actually corresponds to. I
>> suspect it is something other than -mfloat-abi so should I supply this as an
>> extra CFLAG ?
>
> Those are flags that need to be passed to the new gcc that you build,
> when it is run to generate ARM/Maverick code. As far as ct-ng is
> concerned, assuming you're building a usual cross-compiler, they would
> need to be used while cross-compiling the C library that will be used
> on the target system - that is the option you need to locate; it'll
> probably be called LIBCFLAGS or something like that;
>
>       M
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
>

Hi Martin,

thanks for the help.

  CT_LIBC_EXTRA_CC_ARGS: 

  Extra flags to pass gcc when building.
  Seldom used, except for sparc64 which seems to need the flag -64 
                       |
   to be passed onto gcc.

  CT_LIBC_GLIBC_EXTRA_CFLAGS: 

   Extra target CFLAGS to use when building.

I've added the following to the latter option only :
-mfpu=maverick -mfloat-abi=softfp

since -mfpu=maverick is already in CFLAGS, it is probably  a dupe there 
as well.

Does that look like the correct place to put this?

Best regards.

--
For unsubscribe information see http://sourceware.org/lists.html#faq



More information about the crossgcc mailing list