Please test snapshots of the coming R9C

[snickl@REDACTED]

I came across this with gentoo, and I think somebody else has posted about
this issue recently, too:

bash-2.05b$ tar xzf otp_src_P9C_2003-07-09.tar.gz
bash-2.05b$ cd otp_src_P9C_2003-07-09/
bash-2.05b$ export ERL_TOP=`pwd`
bash-2.05b$ uname -a
Linux lucy 2.4.20-gentoo-r2 #27 Tue Apr 22 17:37:20 CEST 2003 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux
bash-2.05b$ ./configure --host=i386-pc-linux-gnu
checking host system type... i386-pc-linux-gnu
checking for GNU make... yes (make)
checking for a BSD compatible install... /bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
creating ./config.status
creating Makefile
configuring in lib
mrunning /bin/sh /home/stefni/dl/otp_src_P9C_2003-07-09/lib/configure  --host=i386-pc-linux-gnu --cache-file=.././config.cache --srcdir=/home/stefni/dl/otp_src_P9C_2003-07-09/lib
akcreating ./config.status
econfiguring in erl_interface/.

running /bin/sh /home/stefni/dl/otp_src_P9C_2003-07-09/lib/erl_interface/./configure  --host=i386-pc-linux-gnu --cache-file=../../.././config.cache --srcdir=/home/stefni/dl/otp_src_P9C_2003-07-09/lib/erl_interface/.
checking host system type... i386-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
[...]
creating ../lib/asn1/c_src/i386-pc-linux-gnu/Makefile
creating i386-pc-linux-gnu/config.h
*********************************************************************
**********************  APPLICATIONS DISABLED  **********************
*********************************************************************

crypto         : No usable OpenSSL found
jinterface     : No Java compiler found
ssl            : No usable OpenSSL found

*********************************************************************
bash-2.05b$ make
cd erts/emulator && ERL_TOP=/home/stefni/dl/otp_src_P9C_2003-07-09 make generate depend
make[1]: Entering directory `/home/stefni/dl/otp_src_P9C_2003-07-09/erts/emulator'
make -f i686-pc-linux-gnu/Makefile generate
make[2]: Entering directory `/home/stefni/dl/otp_src_P9C_2003-07-09/erts/emulator'
make[2]: i686-pc-linux-gnu/Makefile: No such file or directory
make[2]: *** No rule to make target `i686-pc-linux-gnu/Makefile'.  Stop.
make[2]: Leaving directory `/home/stefni/dl/otp_src_P9C_2003-07-09/erts/emulator'
make[1]: *** [generate] Error 2
make[1]: Leaving directory `/home/stefni/dl/otp_src_P9C_2003-07-09/erts/emulator'
make: *** [depend] Error 2


The problem seems to be that the part of the build that makes the
directories "believes" the --host option, while the part that
generates the makefiles goes with autodetection.

This gets you trouble when you want to use binaries on different machines,
but compile (as always) on the fastest around.


CU, SN

-- 
The UNIX equivalent of the "Blue Screen of Death" would be called
"kernel panic". It obviously exists, since I have heard and read about it,
but I've never been witness to it in my professional career.
        John Kirch,
        Networking Consultant and Microsoft Certified Professional (Windows NT)