[okl4-developer] Help regarding the OKL4 port to the Qemu Emulator

Thu Jul 9 15:11:34 EST 2009

Hello,

I downloaded a different version of the toolchain for the
pistachio.Toolchain part after which things started working fine. Amit's
suggestions were also very helpful.

Thanks a lot for the help everyone!

Regards,

Amrit

On Wed, Jul 8, 2009 at 4:28 PM, Gabi Voiculescu <boy3dfx2 at yahoo.com> wrote:

> Hello.
>
> 1. Just to make things perfectly clear for me, can I ask what is the source
> for the two toolchains you currently use:
> - the one to build the kernel
> - the one to build everything else (like this iguana example hello)
>
> Are these built by you? Do you use the recommended binaries (presented
> below)?
>
>
>
> 2. Can you please try to build this example for gumstix ( not only for
> versatile) as well since I did gumstix builds in okl 3 using the tarball
> from the okl4 website recently, and I can confirm that there are no platform
> problems.
> Please use the command:
>
> * tools/build.py machine=gumstix project=examples example=hello
> PYFREEZE=False TOOLCHAIN=gnu_arm_eabi_toolchain
> pistachio.TOOLCHAIN=gnu_arm_toolchaini> BUILD_DIR=build2
>
> BUILD_DIR overwrites the default build directory : build with whatever
> string you say after =, the goal for this is to ensure you do clean build
> for gumstix (no previous "build*" folder). I chose "build2", but you can
> change the string.
>
>
>
>
> 3. You should know the TOOLCHAIN= and pistachio.TOOOLCHAIN= arguments are
> mandatory for any succesfull okl4 3+ build, since the kernel was supposed
> to be compiled with a gcc-3.4.4 based toolchain, and everything else with a
> gcc-4.2.4 based toolchain.
>
>
> Good luck,
> Gabi Voiculescu
>
> PS:  I, personally, have succesfully simulated for the gumstix platform
> using these two publicly available toolchain binaries:
>
> - for the kernel:
> http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.gz
> - for everything as part of your particular example (wether it is this
> iguana example, drivers, oklinux):
> http://wiki.ok-labs.com/downloads/release-3.0/arm-linux-gnueabi-4.2.4.tar.gz
>
> and the skyeye emulator (for gumstix skyeye is implicitly used to simulate
> by okl4 build scripts instead of qemu as the simulation environment since a
> while back ago):
> http://www.ertos.nicta.com.au/downloads/tools/skyeye-kenge-1.2.1n.tar.gz
>
>
>
>
> --- On Wed, 7/8/09, Amrit Acharya <acharyaamrit at gmail.com> wrote:
>
>
> From: Amrit Acharya <acharyaamrit at gmail.com>
> Subject: Re: [okl4-developer] Help regarding the OKL4 port to the Qemu
> Emulator
> To: "Nicholas FitzRoy-Dale" <nfd at cse.unsw.edu.au>, developer at okl4.org
> Date: Wednesday, July 8, 2009, 9:01 AM
>
>
> Hi Nicholas,
>
> I downloaded the official OKL4 3.0 source from the wiki. I tried building
> for the versatile platform using :
>
>  tools/build.py machine=versatile project=examples example=hello
> PYFREEZE=False TOOLCHAIN=gnu_arm_eabi_toolchain and i got the following
> error :
>
> [CXX ] build/pistachio/l4kernel/object/src/init_script.o
> cc1plus: warnings being treated as errors
> pistachio/src/init_script.cc: In function 'void ki_assign_irq(space_t*,
> ki_assign_irq_t*)':
> pistachio/src/init_script.cc:647: warning: type-punning to incomplete type
> might break strict-aliasing rules
> scons: *** [build/pistachio/l4kernel/object/src/init_script.o] Error 1
> scons: building terminated because of errors.
>
> On trying with :
>  tools/build.py machine=versatile project=examples example=hello
> PYFREEZE=False TOOLCHAIN=gnu_arm_eabi_toolchain
> pistachio.TOOLCHAIN=gnu_arm_toolchain , I get the following error:
>
> scons: Reading SConscript files ...
> scons: done reading SConscript files.
> scons: Building targets ...
> [CXX ] build/pistachio/l4kernel/object/src/asid.o
> cc1plus: error: invalid parameter `large-function-growth'
> scons: *** [build/pistachio/l4kernel/object/src/asid.o] Error 1
> scons: building terminated because of errors.
>
> which is the same I was getting while using androidsim and the ported
> version of OKL4.
>
> Amrit
>
>
>
> On Tue, Jul 7, 2009 at 4:27 PM, Nicholas FitzRoy-Dale <nfd at cse.unsw.edu.au<http://mc/compose?to=nfd@cse.unsw.edu.au>
> > wrote:
>
>> Hi Amrit,
>>
>> Thanks for confirming that your build problem occurs for Versatile too. To
>> definitely confirm that the problem is toolchain-related, could you please
>> download the official OKL4 3.0 source from the OKL wiki and verify that you
>> get the same problem building for Versatile? (I am assuming that you tested
>> the Versatile build from the htcdream fork).
>>
>> Doing this will confirm that there is a toolchain problem (if you get the
>> same error) or allow me to narrow down the bug (if you don't get the same
>> error).
>>
>> Nicholas
>>
>>
>> On 07/07/2009, at 8:49 PM, Amrit Acharya wrote:
>>
>>  Hi Nicholas,
>>>
>>> I tried building it again for versatile but I am getting similar errors.
>>> If its a compiler issue, can you direct me to which versions I need to use?
>>> The toolchain I am using is the arm-unknown-linux-gnueabi downloaded from
>>> the OKlabs wiki.
>>>
>>> I tried installing the toolchain again,
>>>
>>> I am now getting the following error when i pass :
>>>
>>> tools/build.py machine=androidsim project=examples example=hello
>>> TOOLCHAIN=gnu_arm_eabi_toolchain pistachio.TOOLCHAIN=gnu_arm_toolchain
>>> PYFREEZE=False
>>>
>>> ...
>>> [CXX ] build/pistachio/l4kernel/object/src/asid.o
>>> cc1plus: error: invalid parameter `large-function-growth'
>>> scons: *** [build/pistachio/l4kernel/object/src/asid.o] Error 1
>>> scons: building terminated because of errors.
>>> ...
>>>
>>> However, if i just pass :
>>>
>>> tools/build.py machine=androidsim project=examples example=hello
>>> PYFREEZE=False TOOLCHAIN=gnu_arm_eabi_toolchain,
>>>
>>> I am still getting the same error which I got initially.
>>>
>>> Amrit
>>>
>>>
>>> On Fri, Jul 3, 2009 at 10:23 PM, Nicholas FitzRoy-Dale <
>>> nfd at cse.unsw.edu.au <http://mc/compose?to=nfd@cse.unsw.edu.au>> wrote:
>>> Hi Amrit,
>>>
>>> This is a problem with the version of the compiler you're using to build
>>> Pistachio. Can you compile for any other targets. For example, can you
>>> compile for gumstix or versatile? If you can build for either of those
>>> targets you should be able to build for androidsim.
>>>
>>> Nicholas
>>>
>>>
>>> On 03/07/2009, at 4:26 PM, Amrit Acharya wrote:
>>>
>>> Hi,
>>>
>>> I have been facing certain problems while trying to build for the Qemu
>>> Emulator.
>>>
>>> I am passing :
>>>
>>> tools/build.py machine=androidsim project=examples example=hello
>>> PYFREEZE=False
>>>
>>> The error I am getting is this :
>>>
>>> ...
>>> ...
>>> ...
>>> > [AR] build/pistachio/lib/libplatform.a
>>> > [LIB] build/pistachio/lib/libplatform.a
>>> > [AR] build/pistachio/lib/libatomic_ops.a
>>> > [LIB] build/pistachio/lib/libplatform.a
>>> > [LINK] build/pistachio/bin/l4lernel
>>>
>>> >
>>> /opt/crosstool/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a(_dvmd_lnx.o):
>>> > In function `__div0':
>>>
>>>
>>> /scratch/philipo/crosstool-0.43/src/gcc-4.2.4/gcc/config/arm/lib1funcs.asm:1000:
>>> undefined reference to `raise'
>>>
>>> >
>>> /opt/crosstool/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a(_divdi3.o):(.ARM.exidx+0x0):
>>> > undefined reference to `__aeabi_unwind_cpp_pr0'
>>>
>>> >
>>> /opt/crosstool/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a(_udivdi3.o):(.ARM.exidx+0x0):
>>> >undefined reference to `__aeabi_unwind_cpp_pr0'
>>>
>>> > scons: *** [build/pistachio/bin/l4kernel] Error 1
>>> > scons: building terminated because of errors.
>>>
>>> I am using the cross-compiler specified in the OK Labs wiki. Also, I came
>>> across another post in the developers forum where it was mentioned : "The
>>> kernel needs to be compiled with the old non EABI toolchain, while the rest
>>> of userland needs to be compiled with the EABI toolchain. To do that you
>>> state :
>>>
>>>  TOOLCHAIN=gnu_arm_eabi_toolchain pistachio.TOOLCHAIN=gnu_arm_toolchain.
>>> "
>>>
>>> I tried this also but I am still getting the same errors. Can I get any
>>> help on fixing this?
>>>
>>> Regards,
>>>
>>> Amrit Acharya
>>>
>>>
>>> _______________________________________________
>>> Developer mailing list
>>> Developer at okl4.org <http://mc/compose?to=Developer@okl4.org>
>>> https://lists.okl4.org/mailman/listinfo/developer
>>>
>>>
>>>
>>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org <http://mc/compose?to=Developer@okl4.org>
> https://lists.okl4.org/mailman/listinfo/developer
>
> *
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20090709/d0cc6332/attachment.htm 