[m-dev.] Can't run configure on ceres

[Ralph Becket]

After a brand new checkout from the repository, I got:


ceres:~/mercury/ws-solver/mercury $ autoconf
ceres:~/mercury/ws-solver/mercury $ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for cygpath... echo
looking for an already installed Mercury compiler to bootstrap with...
checking for mmc...
/home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
checking whether the above mmc works and is sufficiently recent...
configure: error: You need a working Mercury compiler to bootstrap with
no


It works fine on jupiter.  Running the configure script on ceres with
`set -x' added at the top I got:


[...]
looking for an already installed Mercury compiler to bootstrap with...
checking for mmc... + IFS=

+ test -z /home/staff/rafe/bin/i686
+ test -f /home/staff/rafe/bin/i686/mmc
+ IFS=

+ test -z /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin
+ test -f /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
+ ac_cv_path_BOOTSTRAP_MC=/home/ceres/public/mercury-latest/i686-pc-linux-gnu/bi
n/mmc
+ echo 'configure:1631: found /home/ceres/public/mercury-latest/i686-pc-linux-gn
u/bin/mmc'
+ break 2
+ BOOTSTRAP_MC=/home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
+ test -n /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
+ echo 'configure:1643: result: /home/ceres/public/mercury-latest/i686-pc-linux-
gnu/bin/mmc'
+ echo /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
+ test /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc '!=' ''
+ echo 'configure:1651: checking whether the above mmc works and is sufficiently
 recent'
+ echo -n 'checking whether the above mmc works and is sufficiently recent... '
+ cat
/home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc
checking whether the above mmc works and is sufficiently recent... + echo /home/
ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc conftest
+ /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc --verbose --read-c
onfig-file-2003-03-01 --halt-at-warn --linkage static conftest
++ ./conftest
++ tr -d '\015'
+ test 'Hello, world' = 'Hello, world'
+ /home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc --record-term-size
s-as-words --compile-to-c conftest
+ BOOTSTRAP_MC=
+ echo 'configure:1711: result: no'
+ echo no
+ test -f compiler/top_level.c
+ test -f compiler/Mercury/cs/top_level.c
+ test -f /usr/local/mercury-DEV/lib/mercury/bin/i686-pc-linux-gnu/mercury_compi
le
+ test -f /usr/local/mercury-DEV/lib/mercury/bin/i686-pc-linux-gnu/mercury_compi
le.exe
+ echo 'configure:1728: error: You need a working Mercury compiler to bootstrap
with'
+ echo 'configure: error: You need a working Mercury compiler to bootstrap with'
configure: error: You need a working Mercury compiler to bootstrap with
no
+ exit 1


Trying out


/home/ceres/public/mercury-latest/i686-pc-linux-gnu/bin/mmc --record-term-sizes-as-words --compile-to-c conftest


on ceres gives:


mercury_compile: term size profiling is incompatible with high level code


This is rather unfortunate!  Why do we need to check for the
--record-term-sizes-as-words option even if configure is run with
--disable-deep-profiler, which is what I assume it's connected with?
I'd like to find out before I make any changes to the configure script.

-- Ralph
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------