On Mon, Feb 01, 2016 at 11:47:39AM -0600, Bruce Dubbs wrote:
> Dr.-Ing. Edgar Alwers wrote:
> >I am building a new BLFS system, Version SVN-20160101 and I just finished the
> >kdelibs-compilation. Everything is OK. As I had to travel, I installed the
> >image of the new system on my laptop. The system is also working normal
> >there,
> >I can call Fluxbox, xterm, a browser, etc.
> >
> >BUT: I cannot compile anything more:
> >
> >1.) building e.g. "which": when I call "./configure --prefix=/usr", the
> >configure freezes endless, until I type "strg-c"
> >
>
> My best guess is that there is something in the compiler that you built that
> is HW dependent. We would need to see the output of lscpu for both systems.
>
> If you do:
>
> cat > test.c << EOF
> #include <stdio.h>
> int main() { printf( "Testing\n"); }
> EOF
>
> gcc -o testing test.c
>
> ./testing
>
> Does it work?
>
The only hardware-specific thing I recall "recently" was gmp - since
September 2015 I have been using the configfsf.{guess,sub} over the
config. versions. Discussed on the lfs-dev list back then. If that
is the problem, I think you will need to rebuild gmp on the working
system. I think we mention it somewhere in the book, but I cannot
lay my finger on it at the moment.
But try Bruce's suggestion first, it might be something else
entirely. If you actually see 'Internal Compiler Error' messages,
those would suggest bad RAM or flakey hardware (or bad cooling), but
in my experience the compiles fail and stop when those messages
happen.
ĸen
--
This email was written using 100% recycled letters.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
