[okl4-developer] okl4 1.5.2 Build Problems

[Michael P. McCormick]

Hi Nelson,

I found that for some reason, any concatenation of $LINK somehow strips all 
spaces before it and any other string (not just --)

As a temporary work-around, if i hardcode -- ld and append the remaining 
flags, i can get by:

        self.dict["LINKCOM"] = "$ELFADORN -o $TARGET $ELFADORN_FLAGS -- ld 
$_LINK_COM_FLAGS $LINK_PLAT_FLAGS $_LINKADDRESS $_LINKSCRIPTS $LINKFLAGS 
$CRTOBJECT $SOURCES $_LIBFLAGS -o $TARGET"

I know it's cheesy, but at least it works.

On Wednesday 05 March 2008 20:39, Nelson Tam wrote:
> Hi Michael,
>
> On 06/03/2008, at 3:33 PM, Michael P. McCormick wrote:
> > Finally, i downloaded, compiled, and installed python2.4.4, and
> > after making it active, again cleaned the source dir and tried to
> > buiold using the same build command above, this time with
> > python2.4.4 and gcc-3.3.4, yet I still get build errors:
> > <snip>
> >
> > [CC ] build/pistachio/object/libs_gcc/src/__ashrdi3.o
> >
> > [AR ] build/pistachio/lib/libgcc.a
> >
> > [LIB ] build/pistachio/lib/libgcc.a
> >
> > [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.
> >
> > Any help would be appreciated.
>
> This should help you:
>
> http://lists.okl4.org/pipermail/developer/2008-March/000729.html
>
> Also, try building with an additional option "verbose_str=True", which
> tells the build system to output the full compile log.
>
> --
> (nt)
>
> Nelson Tam
> nelson at ok-labs.com

-- 
Thanks,
MikeM