Here's the whole file, inserted into the email: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.50. Invocation command line was $ ./configure --prefix=/opt/kde -disable-static ## ---------- ## ## Platform. ## ## ---------- ## hostname = localhost uname -m = i586 uname -r = 2.4.5 uname -s = Linux uname -v = #1 Tue Aug 14 16:34:58 MST 2001 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = i586 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH = /usr/local/java/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/usr/local/RealPlayer8:/opt/gnome/bin:/opt/www/htdig/bin:/opt/kde/bin:/usr/share/texmf/bin:/usr/openwin/bin ## ------------ ## ## Core tests. ## ## ------------ ## configure:923: PATH=".;."; conftest.sh ./configure: conftest.sh: command not found configure:926: $? = 127 configure:968: checking build system type configure:986: result: i586-pc-linux-gnu configure:993: checking host system type configure:1007: result: i586-pc-linux-gnu configure:1014: checking target system type configure:1028: result: i586-pc-linux-gnu configure:1075: checking for a BSD compatible install configure:1124: result: /usr/bin/ginstall -c configure:1138: checking for -p flag to install configure:1151: result: yes configure:1162: checking whether build environment is sane configure:1205: result: yes configure:1207: checking whether make sets ${MAKE} configure:1227: result: yes configure:1255: checking for working aclocal configure:1262: result: found configure:1270: checking for working autoconf configure:1277: result: found configure:1285: checking for working automake configure:1292: result: found configure:1300: checking for working autoheader configure:1307: result: found configure:1315: checking for working makeinfo configure:1322: result: found configure:1406: checking for a C-Compiler configure:1408: result: configure:1413: checking for gcc configure:1428: found /usr/bin/gcc configure:1436: result: gcc configure:1537: checking whether the C compiler works configure:1543: ./ ./configure: ./: is a directory configure:1546: $? = 126 configure:1553: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. ## ----------------- ## ## Cache variables. ## ## ----------------- ## ac_cv_build=i586-pc-linux-gnu ac_cv_build_alias=i586-pc-linux-gnu ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_host=i586-pc-linux-gnu ac_cv_host_alias=i586-pc-linux-gnu ac_cv_path_install=$'/usr/bin/ginstall -c' ac_cv_prog_CC=gcc ac_cv_prog_make_make_set=yes ac_cv_target=i586-pc-linux-gnu ac_cv_target_alias=i586-pc-linux-gnu ## ------------ ## ## confdefs.h. ## ## ------------ ## #define PACKAGE "mosfet-liquid0.6" #define VERSION "2.2alpha2" configure: exit 1 On Thursday 18 October 2001 05:07 am, you wrote: > Rick Rosinski writes: > > When running configure, I get the following error: > > checking whether the C compiler works... configure: error: cannot run C > > compiled programs. > > If you want to cross compile, use '--host'. > > > > This is weird, since I compile frequently (I avoid binaries quite > > frequently). I haven't added a new compiler since I had installed Slack > > 8.0 > > > > Any ideas? > > I've seen this before, and it had a couple of different causes. You > might have better luck here (or may be able to figure it out yourself) > if you post the last 20 or 30 lines of config.log -- that'll show us > the exact error message. > > john. -- Rick Rosinski http://rickrosinski.com rick@rickrosinski.com