Re: AC_PROG_INSTALL and cross-compilation

[David Burg]

Hello,

I finally wrote a macro that add host_cpu to the path after /usr/local in
the case the user does not provide a specific prefix. The result sounds more
reasonnable, and the the appropriate -Llibpath directive, it avoid inclusion
by the cross-compiler of build machine libraries (which is wrong). By the
way, is it possible to avoid that the cross-compiler try to use libraries of
the building machine ?

Best regards,

David Burg.

----- Original Message -----
From: "Peter Eisentraut" <address@hidden>
To: "David Burg" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, July 10, 2001 4:39 PM
Subject: Re: AC_PROG_INSTALL and cross-compilation


> David Burg writes:
>
> > Still working on cross-compilation. I have solve some portability
trouble so
> > now it is compiling but there are linking trouble. The cause is that the
> > generated library are installed in the wrong path :
> >
> > /usr/local/lib
>
> which is the default for --prefix
>
> > instead of a path like /usr/local/target-cpu/lib
>
> which is just another random possibility
>
> > I know AC_PROG_INSTALL set the path where the files are installed, but
does
> > this macro work with cross-compilation or not ?
>
> AC_PROG_INSTALL only finds the install program and has nothing to do with
> cross-compiling (apart from install -s possibly).
>
> If you want your package to install somewhere other than the default you
> need to use the --prefix option.
>
> --
> Peter Eisentraut   address@hidden   http://funkturm.homeip.net/~peter
>
>