Joseph Maxwell wrote: > Perhaps there is decent kind 'soul' out there willing to take a look and > see if a solution is easily recognizable > log file => > > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:630: checking host system type > configure:651: checking target system type > configure:669: checking build system type > configure:724: checking for a BSD compatible install > configure:777: checking whether ln works > configure:801: checking whether ln -s works > configure:1866: checking for gcc > configure:1979: checking whether the C compiler (gcc ) works > configure:1995: gcc -o conftest conftest.c 1>&5 > gcc: installation problem, cannot exec `as': No such file or directory This is a pretty clear error message, isn't it? GCC tried to execute a program called 'as' (which is the GNU assembler from the binutils package) and it was not available. GCC cannot produce output without an assembler. > But th problem persist, which seems to indicate that was not the problem That is correct, it never was the problem.
