RE: Simple multilib project

[Ralf Corsepius]

2nd attempt to answer (Seems like this mal-configured gnu.org mailserver
refuses to accept mail from me)

On Tue, 2004-05-25 at 18:20, Jon Beniston wrote:
> > 
> > Jon Beniston wrote:
> > > Can anyone point me to a very simple autoconf/automake project that 
> > > builds multilibs for a cross-compiled target? I am having great 
> > > difficulty in getting this to work, as in my project, all the 
> > > libraries get installed on top of each other. (i.e. they all go in 
> > > /lib instead of /target/config/config/lib etc). I'm using autoconf 
> > > 2.59 and automake 1.7.9.
> > 
> > That sounds like the solution will be in the automake space.
>
> I ask here because I hear a few other projects (libstdc++ etc) had a
> similar problem when switching to autoconf 2.57. 

I guess, I know why :)

When comparing automake-1.8.5's config-ml.in to my config-ml.in shipped
with RTEMS (Derived from an older gcc's config-ml.in, hacked to work
with autoconf >= 2.57), I found this:

@@ -101,14 +84,17 @@
  
 Makefile=${ac_file-Makefile}
 ml_config_shell=${CONFIG_SHELL-/bin/sh}
+ml_arguments=${ac_configure_args}
 ml_realsrcdir=${srcdir}
  
 # Scan all the arguments and set all the ones we need.
  
 ml_verbose=--verbose
-for option in ${ac_configure_args}
+for option in ${ml_arguments}
 do
   case $option in
+# Unquote autoconf >= 2.57 added quotes
+  \'--*\') eval option="$option" ;;
   --*) ;;
   -*) option=-$option ;;
   esac


Now, the question is who and how to fix it.

IIRC, automake retrieves config-ml.in from gcc.
The origin of the quoting is autoconf.
The file is shipped with automake.

Ralf