[okl4-developer] Need help in compiling

[Geoffrey Lee]

On Fri, Feb 29, 2008 at 09:50:19AM -0800, Boy Dfx wrote:
> 
> 
> neohtm <neohtm at gmail.com> wrote: Newbie here.....i was having some compilling errors with L4.
> I'd tried tools/build.py and it output the erros as below. Then i downloaded
> the i686-unknow-linux-gnu-gcc from Nicta website and extracted it to /opt/.
> Now how do i need to link this up??
> 
> tools/build.py machine=gumstix project=iguana wombat=yes
> toolprefix=i686-unknown-linux-gnu- scons: Reading SConscript files ...


Hi

If you are compiling for Gumstix, then a i686 target toolchain is 
of course not the right one to use.  :-)  Usually, you do not need
to set the toolprefix from the command line, unless you want to use
a different version o gcc (e.g. one you compiled yourself).

The specific command you see here though is probably because you don't
have the compiler in your PATH.


	-gl

> SERIAL_DRIVER is  uart_8250
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> sh: i686-unknown-linux-gnu-gcc: command not found
> scons: done reading SConscript files.
> scons: Building targets ...
> [CXX ] build/pistachio/l4kernel/object/src/schedule.o
> sh: i686-unknown-linux-gnu-g++: command not found
> scons: *** [build/pistachio/l4kernel/object/src/schedule.o] Error 127
> scons: building terminated because of errors.
> 
> --Neohtm 
> Multimedia University,Malaysia
> 
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> Hi neohtm.
> 
> So you have extracted i686-unknown-linux-gnu-gcc and other stuff in /opt?
> 
> Well. the problem is that by default the OS searches for files only in the folders described in $PATH variable.
> 
> You can check your $PATH variable by typing: echo $PATH
> If you can not see bin folder that contains the executables from the toolchain then you have to add that folder to $PATH each time you open up a new console.
> 
> It will be something like:
> export PATH=$PATH:/opt/{insert your folder path here}/bin 
> 
>        
> ---------------------------------
> Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer


--