'configure' problem

[Till Straumann]

Here's one for you, Ralf:

Built powerpc-mvme2307 with my new toolchain on solaris
and it crashed. I tracked it down to improper
CFLAGS (CPU_CFLAGS is not set).

Here's what happens:

c/src/configure's first line calls for #!/bin/sh

eventually, 'configure' reads the pre-made
'<build_dir>/powerpc-rtems/c/mvme2307/make/mvme2307.cache'

which looks like this (linebreaks added by stupid
message composer):

ac_cv_env_RTEMS_CPU_MODEL=${ac_cv_env_RTEMS_CPU_MODEL=mpc604}
ac_cv_env_RTEMS_BSP_FAMILY=${ac_cv_env_RTEMS_BSP_FAMILY=motorola_powerpc}
ac_cv_env_CPU_CFLAGS=${ac_cv_env_CPU_CFLAGS=-mcpu=604 -mmultiple mstring 
-mstrict-align}
ac_cv_env_CFLAGS_OPTIMIZE_V=${ac_cv_env_CFLAGS_OPTIMIZE_V=-O4}
ac_cv_env_CFLAGS_DEBUG_V=${ac_cv_env_CFLAGS_DEBUG_V=-O1}
ac_cv_env_CFLAGS_PROFILE_V=${ac_cv_env_CFLAGS_PROFILE_V=-O1 }

However, solaris' /bin/sh executing 'configure' doesn't seem to grok the

var=${var=value}

constructs.

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
--Till

PS: I did 'bootstrap' on a different system than the
'configure/build/install' but I thought that should
be OK.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: c-src-configure.gz
Type: application/x-gzip
Size: 39050 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20030403/7fadbde3/attachment.bin>