other/5515: ./configure fails: sed: Function s%@subdirs@% cp cannot be parsed.
Carlo Wood
carlo@alinoe.com
Mon Jan 28 19:21:00 GMT 2002
<guru mode on>
Maybe I can shine a light on this.
One of the reasons that configure fails to substitue
is when
1) A substitution contains new-lines
2) The substitution is exactly overlapping
the border at which the substitution command
is cut into multiple sed commands.
Obviously this a coincidence, but in fact only
truely safe when none of the substitution contain
new-lines.
What the patch below might change is replacing
new-lines in ${subdirs} into spaces.
</guru mode off>
On Mon, Jan 28, 2002 at 09:26:14PM -0500, Craig Rodrigues wrote:
> On Mon, Jan 28, 2002 at 07:50:51PM -0500, Edwin Bates wrote:
> >
> > Fix for file gcc/configure:
> > ---------------------- Begin diff -c -----------------------
> > *** configure.orig Mon Jan 28 19:26:04 2002
> > --- configure Mon Jan 28 19:25:24 2002
> > ***************
> > *** 7353,7358 ****
> > --- 7353,7359 ----
> >
> > trap 'rm -fr `echo "$all_outputs auto-host.h:config.in" | sed "s/:[^
> > ]*//g"` conftest*; exit 1' 1 2 15
> > EOF
> > + subdirs=`echo ${subdirs}`
> > cat >> $CONFIG_STATUS <<EOF
> >
> > # Protect against being on the right side of a sed subst in config.status.
>
>
> Glad you figured it out, but I don't understand why your
> patch fixes things....
> Does the problem go away if you either:
> (1) Set CONFIG_SHELL to /bin/ksh?
> (2) Use GNU sed instead of AIX's sed?
This has nothing to do with sed, but with how
autoconf works.
>
> Thanks.
> --
> Craig Rodrigues
> http://www.gis.net/~craigr
> rodrigc@mediaone.net
--
Carlo Wood <carlo@alinoe.com>
More information about the Gcc-bugs
mailing list