On Tue, 2006-08-08 at 20:18 +0800, Tzu-Chien Chiu wrote: > Hello, Ralf. > > I found gcc and newlib don't use AM_ENABLE_MULTILIB, instead > TARGET_SUBDIR is set. Pardon, they (and binutils) use it.
AM_ENABLE_MULTILIB is used in library subdir configure scripts (*/configure.[ac|in]), not inside of toplevel dirs. > ChangeLog (gcc 3.4.4): > > Thu Jun 19 14:16:42 1997 Brendan Kehoe <[EMAIL PROTECTED]> > > * configure.in: Don't set ENABLE_MULTILIB, so we'll be passing > --enable-multilib down to subdirs; setting TARGET_SUBDIR was enough. > > > I think neither how gcc nor newlib does things is not what I'm looking > for. 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. multilibs means building a library several times for several variants of a host. 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. Ralf
