Graeme,

On Tuesday 31 July 2007 17:07, [EMAIL PROTECTED] wrote:
>  GB> arm-linux-gcc: unrecognized option '-02'
>   JB>                                   ^^^^^ Whats that? Try with -O2 (O
> like octopus, not zero) To be honest I don't know where the -02 (zero-2)
> option is coming from, I assumed it was supplied by ptxdist environment. Is
> that likely ?
> <SNIP...>

If its forwarded by ptxdist it should be forwarded to all packages you 
compile. Does it? If not, its from inside your package.

> GB> /home/wrap/pxaproj1/local/arm-linux/include -isystem
> GB> /home/wrap/pxaproj1/local/arm-linux/usr/include -02 -Os -MT
>                                                   ^^^^^^^
> JB>Choose for -O2 *or* -Os.
> Similar remark, I need to track down where this is coming from.

Sure.

> GB> src/ping_host.c:240: error: impossible constraint in 'asm'
> GB> {standard input}: Assembler messages:
> GB> {standard input}:392: Error: bad instruction `btsl r2,[r3,#-176]'
> JB>Sounds like a toolchain failure. Can you repeat it with one of our
> OSELAS-Toolchains?
>
> How do I setup one of your OSELAS-Toolchains, something 'close to
> arm-linux-gcc-4.1.1' ?

Install also ptxdist-0.10.6 (sorry only with this ptxdist you currently can 
build our toolchains), read 
http://www.pengutronix.de/software/ptxdist/appnotes/AppNote_BuildingToolchain.pdf
and build one of the following toolchains (depends on your target CPU):
 - arm-iwmmx-linux-gnueabi_gcc-4.1.2_glibc-2.5_linux-2.6.18.ptxconfig (PXA270)
 - arm-v4t-linux-gnueabi_gcc-4.1.2_glibc-2.5_linux-2.6.18.ptxconfig (generic)
 - arm-xscale-linux-gnueabi_gcc-4.1.2_glibc-2.5_linux-2.6.18.ptxconfig (Xscale 
CPUs)

Configure your project to use this fresh toolchain and build the project 
again. Maybe it helps.

Juergen

-- 
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
    Handelsregister: Amtsgericht Hildesheim, HRA 2686
         Vertretung Sued/Muenchen, Germany
   Phone: +49-8766-939 228 |  Fax: +49-5121-206917-9

-- 
ptxdist mailing list
[email protected]

Reply via email to