RE: [Sheflug] autoconf help

["Ross" <nospam [at] ntlworld.com>]

> -----Original Message-----
> From: sheflug-bounce@vuw.ac.nz [mailto:nospam [at] vuw.ac.nz]On
> Behalf Of Alex Hudson

> You could also configure for Linux, build the Makefile, and alter it for
> mipsel-linux. That would mean setting CC in the Makefile to
> mipsel-linux-gcc rather than gcc, etc. etc. Since you're just
> retargetting for CPU rather than OS (pretty much) that will do the job.
> You'll also need to point the linker at the mipsel libraries, rather
> than the i386 ones, and at the agenda kernel headers (those are bound to
> be different).
>

this is the route i have taken since the docs don't give explicit
instructions on how to compile for each 'arch'. the resulting binary gives
the correct details for a linux-vr binary when i run 'file madplay'.
something about elf binaries and bit order.... i can't recall exact details
at the mo' but they match with correctly compiled binaries. however, when
executed, the binary sends output to the standard output (terminal)what
looks like the contents of the mp3 file. so during compile, it hasn't
identified the /dev/audio? /dev/audio and sound support within the kernel
are ok as the 'sox' 'play' program compiles and works fine!

during 'make' i still get referance to i686 mainly statements like host=i686
which i presume is normal even for cross compiling?

got any suggestions as to where i should be looking to correct this?
in the kernel include directory, there is a soundcard.h (or .o can't recall
at the mo')so it should have picked up on this from the location of the
include directory specified in the make file?

Thanks
Ross

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.