Problem installing Erlang on Gentoo

snickl@REDACTED snickl@REDACTED
Fri Mar 12 08:49:17 CET 2004


On Thu, 11 Mar 2004, Jimmie Houchin wrote:

> Hello,
>
> I am attempting to emerge erlang on my Gentoo server.
> It is a dual Opteron.

This looks like "the same old problem" (TM) ;)

Gentoo tells the erlang configure the host-type given in make.conf
(x86_64-pc-linux-gnu in your case).
But the erlang configure does also autodetection on the host type,
which may result in something different (x86_64-unknown-linux-gnu here).

One result goes into the Makefiles, the other one into the
directory names for the compile output, if they don't match, bang!

The workaround is to find out what erlang configure has autodetected
for your hostname and to set CHOST accordingly while emerging erlang.

In plain english: CHOST=x86_64-unknown-linux-gnu
Of course, you will want to change it back when finished.


> /var/tmp/portage/erlang-9c-r2/work/otp_src_R9C-0/lib/configure
> --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> --localstatedir=/var/lib --enable-threads --cache-file=.././config.cache
> --srcdir=/var/tmp/portage/erlang-9c-r2/work/otp_src_R9C-0/lib

> make -f x86_64-unknown-linux-gnu/Makefile generate
> make[2]: Entering directory
> `/var/tmp/portage/erlang-9c-r2/work/otp_src_R9C-0/erts/emulator'
> make[2]: x86_64-unknown-linux-gnu/Makefile: No such file or directory
> make[2]: *** No rule to make target `x86_64-unknown-linux-gnu/Makefile'.
>   Stop.

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)



More information about the erlang-questions mailing list