Re: [Ltib] where is the cpu type specified? -> linux kernel build warning

[Lambrecht Jürgen]

I have a strange error during the kernel build (see below): aparently, 
the architecture is not specified ?? (see "-march=" below)
Where is the 'arch' type specified for the kernel in ltib?
(In my platform main.lkc, LINTARCH=arm. So that is OK.)

...
   CC      init/version.o
   CC      kernel/module.o
/usr/src/cross/Linux-svn/init/version.c:0: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
/usr/src/cross/Linux-svn/init/version.c:1: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
/usr/src/cross/Linux-svn/init/version.c:0: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
   LD      init/built-in.o
/usr/src/cross/Linux-svn/kernel/module.c:0: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
/usr/src/cross/Linux-svn/kernel/module.c:1: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
/usr/src/cross/Linux-svn/kernel/module.c:0: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
   LD      kernel/built-in.o
   CC      sound/soc/codecs/mc13783.o
/usr/src/cross/Linux-svn/sound/soc/codecs/mc13783.c:0: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
/usr/src/cross/Linux-svn/sound/soc/codecs/mc13783.c:1: warning: switch 
-mcpu=arm926ej-s conflicts with -march= switch
   LD      sound/soc/codecs/snd-soc-mc13783.o
...

On 11/18/2011 05:53 PM, Peter Barada wrote:
>
> On 11/18/2011 05:50 AM, Lambrecht Jürgen wrote:
> > Hello,
> >
> > I use an arm926ej-s. With gcc, there is the option '-mcpu=926ej-s'.
> > For the moment, this is only specified in the linux config
> > ('CONFIG_CPU_ARM926T=y').
> > Is it not necessary to add '-mcpu=926ej-s' to the global compile options
> > in ltib (CONFIG_TOOLCHAIN_CFLAGS)?
> > (this is not done for imx27pdk, or for any imx platform)
> >
> > Kind regards,
> >
> Look in your platform main.lkc, you should see "config CPU" as a string
> (w/no prompt making it a constant).
>
> Befor you change your CPU definition, you'll have to track down all the
> places where its used, both in .lkc files and .spec files.
>
The CPU is MX27, seems not to be really used.
In the same file, GNUTARCH=LINTARCH=arm. So that is OK.
>
>
> What could be simpler is to look in config/userspace/toolchain.lkc,
> specifically TOOLCHAIN_CFLAGS.  Depending on the toolchain selected it
> will change the CFLAGS used by most packages.  You can add another
> configuration bool in config/userspace/toolchain.lkc that defines
> whether you are running on an arm926ej-s, and then use that bool to
> decide whether to deffault TOOLCHAIN_CFLAGS with "-mcpu=926ej-s" or not
>
I set custom flags; could indeed add it in toolchain.lkc.

Thanks,
Jürgen
>
> - be careful as you may need multiple permutations to handle all the
> combinations.
>
> Then the next time you run ./ltib -c you can specify the new flag (or
> not) - and if you set things up correctly you'll see "-mcpu=926ej-s" in
> CONFIG_TOOLCHAIN_CFLAGS in your platform .config file (as well as see it
> used on packages that get built)...
>
> No guarantee it will work, but give it a whirl and see what happens.
> Worse case would be that you have to undo your changes and rebuild from
> scratch to get back to where you currently are...
>
> --
> Peter Barada
> address@hidden
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>


-- 
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk