'configure' problem

Ralf Corsepius corsepiu at faw.uni-ulm.de
Mon Apr 7 16:00:18 UTC 2003

Am Fre, 2003-04-04 um 06.51 schrieb Till Straumann: 
> Here's one for you, Ralf:

> However, solaris' /bin/sh executing 'configure' doesn't seem to grok the
> var=${var=value}
> constructs.
Well, var=${var=value} is the construct having been used for autoconf's
config caches for years, but ...

... I can reproduce the problem ...

The problem seem to be Solaris /bin/sh having problems in parsing quotes
(There even is a paragraph related to this issue in autoconf.info :( )

It accepts 

but it chokes on
a=${a=-X -Y}

a=${a="-X -Y"}

also seems to work ...

> configure complains but runs through (and the complaint went
> undetected) but fails to build a correct Makefile
> (i.e. it builds a Makefile but doesn't set CPU_CFLAGS).
> Any ideas about what went wrong greatly appreciated

I don't recall the rationale for autoconf using a=${a=...}, wo let's try
the normal, nominal way of "/bin/sh" setting up vars ....

Can you try the patch below?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtems-rc-20030407-1.diff
Type: text/x-patch
Size: 1254 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20030407/acfaaee4/attachment-0001.bin>

More information about the users mailing list