Re: cross compil expat on ARM7

* BRACH Vincent <[email protected]> wrote:

<snip>
> I'm trying to cross-compil expat (just librarie static & shared) from my
> host (i686-pc-linux-gnu) for an ARM7 target (S3C44B0X running on
> uClinux)
> 
> I fixed the environnement variables follow :
> 
> export CC="arm-elf-gcc"
> 
> export CFLAGS="-DUNIX=1 -DMWPIXEL_FORMAT=MWPF_TRUECOLOR0888 -O2
> -fomit-frame-pointer -Dlinux -D__linux__ -Dunix -D__uClinux__ -DEMBED
> -fno-builtin -I/home/vincent/uClinux-dist/linux-2.4.x/include -I." 
> 
> export LDFLAGS="-Wl,-elf2flt
> -nostartfiles /home/vincent/uClinux-dist/lib/uClibc/lib/crt0.o /home/vincent/uClinux-dist/lib/uClibc/lib/crti.o /home/vincent/uClinux-dist/lib/uClibc/lib/crtn.o -L/home/vincent/uClinux-dist/lib/uClibc/. -L/home/vincent/uClinux-dist/lib/uClibc/lib"

You shouldn't go this obscure ways. 
Use a sysroot'ing (cross-)toolchain instead. 
crosstool is your friend.

expat now builds quite good in sysroot-environments. 
it's not complex enough that libfool makes headaches. 
(aka doesnt import other libraries)

for other packages with more complex dependencies (ie. x11-mod)
you gonna need a fixed libtool (hah, will this ever be done ? ;-P)
or my own implementation (which is in fact an frontend to an *real*
toolchain abstraction) ...

> I have normaly the messages : "checking whether the C compiler works...
> configure: error: cannot run C compiled programs.

Probably it passes the wrong options to gcc and so mixes up both
environments.

> If you meant to cross compile, use `--host'."
> 
> But I don't know what I must give for argument "host" ???

Its really cute that autoshit tries to provide some way for passing
another platform, but to make this work, you have to put your 
cross compiler into some "standard location" (next to the other one), 
but this allows only *one* crosscompiler per platform identifier
(that doesn't work for me - i've got a dozen ones for just for linux-i686)
and I also wouldn't risk this messing up you toolchain ... 

This *should* tell autoshit to use different toolchains for 
built-in programs run by the compile process (yeah, such stupid 
things really exist !) vs. the actual package code.

I've got a reason for choosing the word "should" ...

> I try " ./configure --prefix=/home/vincent/uClinux-dist/lib/libexpat
> --host=arm " but I don't think it's the good way !

Yeah, thats how its meant to work.  Meant to.


BTW: I'm currently developing something to get rid of autoshit+libfool,
something which just uses some small and strictly defined textfile 
as input, something not trying to do a weather forecast in a shell script,
something thats working absolutely deterministic, something reliable ...
Perhaps someday someone's interested in in, someone beside me.

<snip>

> (I'm not yet subscriber of mailing list "[email protected]"
> please just mail me to [email protected] (or reply))

you better should subscribe. makes life easier.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     [email protected]
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------