I used to cross-compile all the time. It seems that you need to set CC,
CXX, AR, AS, RANLIB, LD and BUILD_CC as well as addeding to your path
the directory where the binutils for cross-compiling can be found.
Give it another shot.
On 17 Jul 2001 14:06:57 -0400, Brian S. Julin wrote:
>
> On Tue, 17 Jul 2001, Brian S. Julin wrote:
> > Hmm,
> >
> > Even when given a --target=hppa-linux ./configure still
>
> Sorry, I meant --host=hppa-linux (and --build=i386-linux, in this case).
>
> And, now that I think of things, I am not so sure at all
> what the correct behavior is supposed to look like. None of the
> packages I have cross-compiled before (the toolchain and libc
> that is) used external libs other than libc; and a search path
> for the cross-libc is given on the commandline when building those.
>
> Configure must know not to look for .so files in the normal system
> directories because they are the wrong arch, and then where should it look
> for cross-svgalib, for example?
>
> It would not be horribly important, except that a lot of GGI's potential
> user base are embedded systems people who would strongly prefer not
> to have to compile natively, given they are compiling for weak-arm
> processors. Also, given the cygwin slowness issue, cross compiling
> there could be a help (I notice there are bits and peices about that
> in configure.in already.)
>
> I should download something else I know that people likely cross compile,
> like fileutils, and see what it does, or maybe Thayne has experience with
> this already?
>
> --
> Brian
--
Thayne Harbaugh
