Thank you. You're right. It has nothing to do with multilib.
I've read configure.ac and Makefile.am of texinfo. Here is how it works.
When cross-compiling, the same configure script is run twice for all
sub-directories of source directory. Makefile.am, however, selectively only
builds some or all of these sub-directories depending upon if set TOOLS_ONLY
is set by the configure script. When building native tools, the variables
CC, AR, and RANLIB copied from the their BUILD_* environment variable
counterparts.
The users have to manually set BUILD_CC, BUILD_AR, BUILD_RANLIB before
running 'configure', right? I thought there would be AC_PROG_*-like macros
for these?
2006/9/21, Stepan Kasal <[EMAIL PROTECTED]>:
Hello,
Ralf Corsepius has answered the question about AM_ENABLE_MULTILIB,
and then, on Thu, Sep 21, 2006 at 09:52:25AM +0200, he wrote:
> > I need to build *both* the native and the cross-compiled library
> > at the same time (one-time configure script and make), rather than
> > *either one* of them.
> This is a completely different problem and not related to multilibs at
> all. [...]
> What you are looking for is simultaneously building for the build system
> (native) and for the host (cross). Only very few packages support this.
> autoconf/automake doesn't support it by themselves.
my previous answer targeted this second problem (as I do not have
any experience with multilib).
I'm guess the basic tools packages, like binutils and gcc, have to
support a ``bootstrap'' which involves this. But these packages are
too complex.
That's why I suggested to study texinfo/configure.ac (from version
4.8 or newer), which does build a couple of native tools, which are
then needed for the main cross-platform build.
Texinfo is a smaller package, and thus should serve as a more
comprehensive example. Feel free to ask me about the details of it.
HTH,
Stepan Kasal
--
Tzu-Chien Chiu - SMedia Technology Corp.
URL: http://www.csie.nctu.edu.tw/~jwchiu/
