On 03/24/2011 01:55 PM, Julien Heyman wrote:
> Hi Adam,
>
> Thank you for your input.
> I tried doing just that (make L4ARCH=arm O=../../obj/l4linux/arm-up) right
> after a fresh full/default build of the snapshot, and without changing
> anything in the L4linux kernel config yet, and I get this:
>
> bids@bids-desktop:~/Fiasco.OC/l4re-snapshot-2011022209/src/l4linux$ make
> L4ARCH=arm O=../../obj/l4linux/arm-up
> Using /home/bids/Fiasco.OC/l4re-snapshot-2011022209/src/l4linux as source
> for kernel
> GEN
> /home/bids/Fiasco.OC/l4re-snapshot-2011022209/obj/l4linux/arm-up/Makefile
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CC kernel/bounds.s
> cc1: error: unrecognized command line option "-mabi=apcs-gnu"
> cc1: error: unrecognized command line option "-mapcs"
> cc1: error: unrecognized command line option "-mno-sched-prolog"
> /home/bids/Fiasco.OC/l4re-snapshot-2011022209/src/l4linux/kernel/bounds.c:1:
> error: bad value (armv4t) for -march= switch
> /home/bids/Fiasco.OC/l4re-snapshot-2011022209/src/l4linux/kernel/bounds.c:1:
> error: bad value (arm9tdmi) for -mtune= switch
> make[2]: *** [kernel/bounds.s] Error 1
> make[1]: *** [prepare0] Error 2
> make: *** [sub-make] Error 2
>
> What am I doing wrong ?
>
> Thanks,
> Julien
>
>
> On Wed, Mar 23, 2011 at 10:20 PM, Adam Lackorzynski <
>
adam@os.inf.tu-dresden.de> wrote:
>
>> Hi,
>>
>> On Wed Mar 23, 2011 at 14:27:35 +0100, Julien Heyman wrote:
>>> I would appreciate getting some advice as to the proper way to customize
>> and
>>> rebuild an L4Linux kernel.
>>> I am testing Fiasco.OC/L4Re/L4Linux on a Beagleboard (ARM), I installed
>>> everything from the latest snapshot package, full build is fine, and
>>> launching the provided L4Linux "arm-up" kernel on my Beagleboard is ok.
>>> Now, to customize the configuration of the L4Linux kernel, I did "*make
>>> O=../../obj/l4linux/arm-up menuconfig*" from *\src\l4linux* directory,
>>> adjusted a few options, saved & exited, so far so good.
>>> Then I try to rebuild the L4Linux kernel using "*make
>>> O=../../obj/l4linux/arm-up*", and I get:
>>
>> For ARM, it's:
>> make L4ARCH=arm O=../../obj/l4linux/arm-up
>>
>>> *"<path...>/src/l4linux is not clean, please run 'make mrproper'
>>> in the '<path...>/src/l4linux' directory."*
>>>
>>> So I do just that,
>>> *
>>> <path..>/src/l4linux$ make O=../../obj/l4linux/arm-up mrproper*
>>>
>>> but :
>>> - it ends with an error *"rm: cannot remove
>> `arch/l4/include/asm/orig-arch':
>>> Is a directory"*
>>> - as expected, it wipes out a lot of things in the target build
>> directory,
>>> including... the *.config* corresponding to my customized kernel....back
>> to
>>> square one.
>>
>> Yes, that's what 'mrproper' is doing.
>>
>>
>>
>>
>> Adam
>> --
>> Adam
adam@os.inf.tu-dresden.de
>> Lackorzynski
http://os.inf.tu-dresden.de/~adam/
>>
>> _______________________________________________
>> l4-hackers mailing list
>>
l4-hackers@os.inf.tu-dresden.de
>>
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>>
>
>
>
> _______________________________________________
> l4-hackers mailing list
>
l4-hackers@os.inf.tu-dresden.de
>
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers