From: Andrzej O. <an...@ma...> - 2009-01-13 01:06:59
|
Hi, Maybe it is temporary, but some days ago build stopped on ntop and after updates on Jan 12 build stops on new binutils? How do You think? maybe my compiler is to old? I obtain: > + /build/tmp/binutils-2.18/configure --prefix=/usr --localstatedir=/var --enable-shared --disable-werror > checking build system type... i586-pc-linux-gnu > checking host system type... i586-pc-linux-gnu > checking target system type... i586-pc-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln works... yes > checking whether ln -s works... yes > checking for gcc... gcc -D_FORTIFY_SOURCE=0 > checking for C compiler default output file name... configure: error: C compiler cannot create executables > See `config.log' for more details. and in /build/tmp/binutils-build/config.log > configure:3090: checking for C compiler version > configure:3093: gcc -D_FORTIFY_SOURCE=0 --version </dev/null >&5 > gcc (GCC) 4.1.2 > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > configure:3096: $? = 0 > configure:3098: gcc -D_FORTIFY_SOURCE=0 -v </dev/null >&5 > Using built-in specs. > Target: i686-pc-linux-gnu > Configured with: ../gcc-4.1.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++ > Thread model: posix > gcc version 4.1.2 > configure:3101: $? = 0 > configure:3103: gcc -D_FORTIFY_SOURCE=0 -V </dev/null >&5 > gcc: '-V' must come at the start of the command line > configure:3106: $? = 1 > configure:3129: checking for C compiler default output file name > configure:3132: gcc -D_FORTIFY_SOURCE=0 -mtune= -march= conftest.c >&5 > cc1: error: missing argument to "-mtune=" > cc1: error: missing argument to "-march=" > configure:3135: $? = 1 > configure: failed program was: > | /* confdefs.h. */ > | > | #define PACKAGE_NAME "" > | #define PACKAGE_TARNAME "" > | #define PACKAGE_VERSION "" > | #define PACKAGE_STRING "" > | #define PACKAGE_BUGREPORT "" > | /* end confdefs.h. */ > | > | int > | main () > | { > | > | ; > | return 0; > | } > configure:3174: error: C compiler cannot create executables Best regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Heiko Z. <he...@zu...> - 2009-01-13 01:13:50
|
Quoting Andrzej Odyniec <an...@ma...>: > Hi, > > Maybe it is temporary, but some days ago build stopped on ntop and after > updates on Jan 12 build stops on new binutils? How do You think? maybe my > compiler is to old? > > I obtain: > >> configure:3129: checking for C compiler default output file name >> configure:3132: gcc -D_FORTIFY_SOURCE=0 -mtune= -march= conftest.c >&5 >> cc1: error: missing argument to "-mtune=" >> cc1: error: missing argument to "-march=" I added some additional config to "make menuconfig", you can now choose optimizations for specific CPUs under the build configuration. Keep in mind that DL doesn't support cross-compiling, you actually have to have a compatible CPU in your build machine! Add this line to your .config: CONFIG_GCC_CPU=i586 Or change it to whatever you want via make menuconfig. Other then i486-i686 is not very well tested, so please provide feedback if you run into problems. I finished a full compile with 'k8' and it seems to work. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Oliver N. <dig...@gm...> - 2009-01-13 14:36:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrzej Odyniec schrieb: > Hi, > > Maybe it is temporary, but some days ago build stopped on ntop and after > updates on Jan 12 build stops on new binutils? How do You think? maybe my > compiler is to old? I had the same problems when i tried to compile the development release. It is very useful to set the following option in your .config file: CONFIG_DISABLELOGGING=y (yes, the naming of this option is extremly weird!) It is confusing, but this ENABLES logging during compile. This is important when you have to answer some questions about new Kernel features, which causes the buildprocess seem to "hang" because you don't answer the question(s). After a complete remove of my lfssystem and enabling the above option, my setup build nicly and i have now a fresh DL-1.3.7 ;-) Hope that helps, Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJbKbF724ZL5LNhNcRAg1sAJ0aThP46AV8NX7+wfUD+gJnpzwNHwCfRQ3S R93W8QUqdUq0GtgPnC+p4uM= =uOT2 -----END PGP SIGNATURE----- |
From: Andrzej O. <an...@ma...> - 2009-01-13 15:57:33
|
Oliver Niesner: > I had the same problems when i tried to compile the development release. > > It is very useful to set the following option in your .config file: > > CONFIG_DISABLELOGGING=y (yes, the naming of this option is extremly weird!) > > It is confusing, but this ENABLES logging during compile. Enables to console... but disables logging to files in directory /build/tmp/LOGS/... I think, cause of this is named DISABLELOGGING > This is important when you have to answer some questions about new Kernel features, > which causes the buildprocess seem to "hang" because you don't answer the question(s). I solve this looking on compilation process on one PuTTY screen and when "hangs", then on second screen I display according log file, i.e. tail -f /usr/src/lfssystem/build/tmp/LOGS/build/grsecurity and answer on the first screen to the questions on second :) Additionally I have logs in files and I can reference to this files, when some phase fails. > After a complete remove of my lfssystem and enabling the above option, my setup build > nicly and i have now a fresh DL-1.3.7 ;-) > > Hope that helps, Thanks, Oliver. This time problem was solved by the hint from Heiko. This new Heiko option "CONFIG_GCC_CPU=" was by default set empty in .config Setting it to the CONFIG_GCC_CPU=i586 solved this problem and full build process ended some minutes ago. Now I run make install. Regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |