[okl4-developer] building for ia32_pc99 (newbie)

[Nelson Tam]

Hi Herbert,

On 03/03/2008, at 4:05 PM, Herbert Bos wrote:

> Hi, this is a newbie question re: okl4 on ia32_pc99. I am using OKL4
> version 1.5.2 from the ok-labs website.
>
> First, i had some minor problems with toolchains.py.
>
> - I am using gcc4.1.3 alongside the gcc3.3 needed for the build, but
> when I specify toolsuffix=-3.3, the script adds the suffix to all  
> tools
> (including ar, ranlib, etc). I fixed this manually in toolchains.py   
> so
> that the suffix is only added where needed
>
> - also, I edited  toolchains.py to not use the "i686-unknown-linux- 
> gnu-"
> prefix, by specifying:
> gnu_ia32_toolchain = generic_gcc("")
>
> I suppose both of the above edits are frowned upon, and I guess there
> are better way doing this, but I did not find them. Any hints?
>

I would recommend using the NICTA distributed toolchains, for  
simplicity.

>
> Second (and hopefully unrelated to this), the build fails as follows  
> at
> link time:
>
> [LINK] build/pistachio/bin/l4kernel
> Usage: elfadorn [options] -- <linker> [linker_options]
>
> elfadorn: error: no such option: --ld
> scons: *** [build/pistachio/bin/l4kernel] Error 2
> scons: building terminated because of errors.
>

Can you please check, in tools/toolchain.py, for the  
self.dict["LINKCOM"] variable?  This defines the arguments passed to  
elfadorn.  It should be something like:

self.dict["LINKCOM"] = "$ELFADORN -o $TARGET $ELFADORN_FLAGS --  
$UNADORNED_LINKCOM"

Is there a space between "--" and "$UNADORNED_LINKCOM"?

> Any clues? [python version 2.4  is installed. I tried debugging  
> elfadorn
> but it is a bit too hairy and I don't really speak python]
>
> As always, all help greatly appreciated.
> Cheers,
> Herbert


--
(nt)

Nelson Tam
nelson at ok-labs.com