On Mon, Apr 29, 2013 at 06:57:42PM +0200, Dr.-Ing. Edgar Alwers wrote: > configure:3801: gcc -V >&5 > gcc: error: unrecognized command line option '-V' > gcc: fatal error: no input files > compilation terminated. > ------------------- > unquote > > There are several "compilation terminated" in this log. If > needed, I can provide the complete file as an internet file. > No ideas about your problem (I don't use wifi on my LFS machines, and so far I haven't been tempted to try to build my own kernel for my netbook which is running 'buntu with nm, let alone sort it out enough to make building LFS a realistic option there).
But I think you need to understand that the output from configure will show _many_ failed compiles. The main purpose of configure is to detect the variations of your system. Most of these are related to the host OS (OSX, sometimes cygwin, various BSDs, various "real" unix versions), another group are related to variations in which libraries are needed for certain functionality, or whether a particular library version contains a certain function or needs another library to link. The result is that *any* config.log which succeeds enough for the package to build will show *many* failures. Do you have build logs (particularly, the output from configure) for the current build and for a recent known-good build ? If so, try comparing the configure output (side by side in xterms or similar, if you like) to see if any test got a different result. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
