Re: [blfs-support] Internal compiler error ? SOLVED

[Michael Shell]

On Thu, 03 Mar 2016 17:20:26 +0100
"Dr.-Ing. Edgar Alwers"  wrote:

> Again, thank you very much  Bruce, Ken and Michael for the help


  Edgar,

And my apologies for not replying sooner - I was busy with other things
and got behind on all my mailing list email.


  Cheers,

  Mike

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ? SOLVED

[Dr.-Ing. Edgar Alwers]

> On Tuesday 02 February 2016 23:14:16 Michael Shell wrote:
> > : cat /proc/cpuinfo
> > 
> > In this way, Edgar can compare the CPUs of his two machines. I bet they
> > differ with regard to bmi2 capability
> 

Following Michael Shell's E-Mail :
--
The offender turned out to be the mulx instruction:
https://www.mailarchive.com/blfssupp...@lists.linuxfromscratch.org/msg02228.html[1]
--
I changed in the gmp-6.1.0 source "config.guess" around line 815 to
modelstr = " coreisbr";

and in
"mpn/x86_64/fat/fat.c"  around line 293 I deleted the statement 
"if ((dummy_string[0 + 8 / 8] & (1 << (8 % 8))) != 0)
CPUVEC_SETUP_coreihwl; "

With this changes, the image of the PC could be moved to the laptop, and the 
laptop compiler 
worked. 

It is remarkable that the problem with the freezing ./configure ( my E-Mail 
1.2.2016 ) was also 
related to gmp and also solved. Furthermore I am working with gmp-6.1.0 and not 
with 6.0.0a. 
This means, that the problem has not been solved yet in a general form.

The problem is important: I need the posibility of changing the installed 
system on the laptop, 
e.g to introduce wireless connections which I do not need on my PC, which is 
connected by 
wire.

I intend to create a short E-Mail with a different subject  " porting LFS/BLFS 
to another machine", 
as the actual subject does not reflect the real problem of porting systems.

Again, thank you very much  Bruce, Ken and Michael for the help

Edgar




-- 
Dr.-Ing. Edgar Alwers 
GPG Key ID:AD5C6F70


[1] 
https://www.mail-archive.com/blfs-support@lists.linuxfromscratch.org/msg02228.html
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Dr.-Ing. Edgar Alwers]

On Tuesday 02 February 2016 23:14:16 Michael Shell wrote:

> : cat /proc/cpuinfo
> In this way, Edgar can compare the CPUs of his two machines. I bet they
> differ with regard to bmi2 capability

I am now at home and can take a look at my PC. May I come back to this issue ?

As Michael assumed, my two machines differ with regard to the bmi2 capability:
Results of cat /proc/cpuinfo:

For the PC:
quote
---
Architektur:   i686
CPU Operationsmodus:   32-bit, 64-bit
Byte-Reihenfolge:  Little Endian
CPU(s):4
Liste der Online-CPU(s):0-3
Thread(s) pro Kern:2
Kern(e) pro Socket:2
Sockel:1
Anbieterkennung:   GenuineIntel
Prozessorfamilie:  6
Modell:60
Modellname:Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
Stepping:  3
CPU MHz:   3600.000
Maximale Taktfrequenz der CPU:3600,
Minimale Taktfrequenz der CPU:800,
BogoMIPS:  7183.63
Virtualisierung:   VT-x
L1d Cache: 32K
L1i Cache: 32K
L2 Cache:  256K
L3 Cache:  3072K
Markierungen:  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp lm 
constant_tsc 
arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq 
dtes64 
monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 
movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm arat epb pln pts 
dtherm tpr_shadow 
vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid 
xsaveopt
---
unquote

and for the laptop, as already mentioned in my E-Mail dated 1.2.2016 
quote

Architektur:   i686
CPU Operationsmodus:   32-bit, 64-bit
Byte-Reihenfolge:  Little Endian
CPU(s):4
Liste der Online-CPU(s):0-3
Thread(s) pro Kern:2
Kern(e) pro Socket:2
Sockel:1
Anbieterkennung:   GenuineIntel
Prozessorfamilie:  6
Modell:58
Modellname:Intel(R) Core(TM) i3-3227U CPU @ 1.90GHz
Stepping:  9
CPU MHz:   1800.000
Maximale Taktfrequenz der CPU:1901,
Minimale Taktfrequenz der CPU:779,
BogoMIPS:  3791.43
Virtualisierung:   VT-x
L1d Cache: 32K
L1i Cache: 32K
L2 Cache:  256K
L3 Cache:  3072K
Markierungen:  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp 
lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf 
eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida 
arat epb pln 
pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt

unquote 

As Bruce advised, I rebuilt gmp on the PC according to his instructions 
2.2.2016:

./configure --prefix=/usr\
 --enable-cxx \
 --disable-static \
 --docdir=/usr/share/doc/gmp-6.1.0
etc

and then installed the image on the Laptop. The image works on the laptop, but 
building of 
programs is still not possible. Configure is OK, but make crashes with the old  
"internal compiler 
error".

Michael mentioned a patch for gmp. Could you give me a little hint, how to 
procede ? A problem 
with the laptop can be excluded, as I can run perfectly  program buildings from 
another, older 
partition.

Thank you again for the help,-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Dr.-Ing. Edgar Alwers]

On Tuesday 02 February 2016 23:14:16 Michael Shell wrote:

> In this way, Edgar can compare the CPUs of his two machines. I bet they
> differ with regard to bmi2 capability.

As a first information, my laptop on which I am having the problems does not 
list "bmi2". I actually cannot check my PC  !

Thanks a lot for the very interesting link. I shall see what I can do  with 
gmp and report then.

Edgar

-- 
Dr.-Ing. Edgar Alwers 
GPG Key ID:AD5C6F70
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Dr.-Ing. Edgar Alwers]

On Monday 01 February 2016 22:31:32 Bruce Dubbs wrote:

> Try figuring out where configure is giving the problem and comment that 
> part out.  It's jsut a bash script.

configure goes endless executing the following statements:
quote
-
  # If we had to re-execute with $CONFIG_SHELL, we're ensured to have
  # already done that, so ensure we don't try to do so again and fall
  # in an infinite loop.  This has already happened in practice.
  ## _as_can_reexec=no; export _as_can_reexec
  # Don't try to exec as it changes $[0], causing all sort of problems
  # (the dirname of $[0] is not the place where we might find the
  # original and so on.  Autoconf is especially sensitive to this).
  ## . "./$as_me.lineno"
  # Exit status is that of the last command.
  ## exit
}
-
unquote
I commented out the  "##" statements. After that, configure worked.

However, the configuration of gmp-6.1.0 failed with a statement
" configure: error: could not find a working compiler, see config.log for 
details"

I include the full result of the configuration ( "configure-result" ) as well 
as the "config.log". May be you can analyse in some way what is happening

Again, thank you very much,
Edgar

-- 
Dr.-Ing. Edgar Alwers 
GPG Key ID:AD5C6F70./configure: line 946:  8245 Illegal instruction expr "x$ac_useropt" : 
".*[^-+._$as_cr_alnum]" > /dev/null
./configure: line 946:  8250 Illegal instruction expr "x$ac_useropt" : 
".*[^-+._$as_cr_alnum]" > /dev/null
checking build system type... ivybridge-pc-linux-gnu
checking host system type... ivybridge-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=32
checking compiler gcc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long 
reliability test 1
checking compiler gcc -O2 -pedantic -fomit-frame-pointer ... no, long long 
reliability test 1
checking compiler icc -no-gcc ... no
checking whether cc is gcc... yes
checking compiler cc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long 
reliability test 1
checking compiler cc -O2 -pedantic -fomit-frame-pointer ... no, long long 
reliability test 1
configure: error: could not find a working compiler, see config.log for details

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GNU MP configure 6.1.0, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --prefix=/usr --enable-cxx --disable-static --docdir=/usr/share/doc/gmp-6.1.0

## - ##
## Platform. ##
## - ##

hostname = edgar2
uname -m = i686
uname -r = 4.3.3
uname -s = Linux
uname -v = #1 SMP Fri Jan 15 21:27:00 CET 2016

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /opt/qt4/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/kde/bin
PATH: /opt/qt4/bin
PATH: /usr/bin
PATH: /sbin
PATH: /usr/local/bin
PATH: /opt/bin
PATH: /usr/local/sbin
PATH: /usr/bin
PATH: /lib
PATH: /opt/qt/bin
PATH: /opt/qt4/bin
PATH: /opt/kde
PATH: /opt/kde/bin
PATH: /opt/jdk-7u3
PATH: /opt/jdk-7u3/bin


## --- ##
## Core tests. ##
## --- ##

configure:3055: checking build system type
configure:3069: result: ivybridge-pc-linux-gnu
configure:3089: checking host system type
configure:3102: result: ivybridge-pc-linux-gnu
configure:3139: checking for a BSD-compatible install
configure:3207: result: /usr/bin/install -c
configure:3218: checking whether build environment is sane
configure:3273: result: yes
configure:3424: checking for a thread-safe mkdir -p
configure:3463: result: /bin/mkdir -p
configure:3470: checking for gawk
configure:3486: found /usr/bin/gawk
configure:3497: result: gawk
configure:3508: checking whether make sets $(MAKE)
configure:3530: result: yes
configure:3559: checking whether make supports nested variables
configure:3576: result: yes
configure:3705: checking whether to enable maintainer-specific portions of Makefiles
configure:3714: result: no
User:
ABI=32
CC=
CFLAGS=(unset)
CPPFLAGS=(unset)
MPN_PATH=
GMP:
abilist=64 x32 32
cclist=gcc icc cc
configure:5749: gcc 2>&1 | grep xlc >/dev/null
configure:5752: $? = 1
configure:5806: checking compiler gcc -m32 -O2 -pedantic -fomit-frame-pointer 
Test compile: 
configure:5820: gcc -m32 -O2 -pedantic -fomit-frame-pointer  conftest.c >&5
configure:5823: $? = 0
configure:5828: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:5831: $? = 0
Test 

Re: [blfs-support] Internal compiler error ?

[Michael Shell]

On Mon, 1 Feb 2016 20:05:11 +
Ken Moffat  wrote:

> 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.


Yeah, I sure do remember that ordeal as I participated in it:

https://www.mail-archive.com/blfs-support@lists.linuxfromscratch.org/msg02166.html

and as the thread went on we finally tracked down the specific
illegal instruction.

The offender turned out to be the mulx instruction:

https://www.mail-archive.com/blfs-support@lists.linuxfromscratch.org/msg02228.html

and therein is a patch for the gmp source to lockout the use of bmi2
instruction set (of which mulx is one). 

Also, note from my post a way to check to see if a CPU supports
the bmi2 instruction set:

: cat /proc/cpuinfo
:
: To support mulx, the CPU must list bmi2 in the cpuinfo flags section:
:
: 
http://unix.stackexchange.com/questions/43539/what-do-the-flags-in-proc-cpuinfo-mean
:
: (see under "Intel-defined CPU features, CPUID level 0x0007:0 (ebx)")


In this way, Edgar can compare the CPUs of his two machines. I bet they
differ with regard to bmi2 capability.


  Cheers,

  Mike Shell


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Ken Moffat]

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 
> 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

Re: [blfs-support] Internal compiler error ?

[Dr.-Ing. Edgar Alwers]

On Monday 01 February 2016 11:47:39 Bruce Dubbs wrote:

> 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.

I can only give the result for the laptop, as I am far from my PC:
quote

Architektur:   i686
CPU Operationsmodus:   32-bit, 64-bit
Byte-Reihenfolge:  Little Endian
CPU(s):4
Liste der Online-CPU(s):0-3
Thread(s) pro Kern:2
Kern(e) pro Socket:2
Sockel:1
Anbieterkennung:   GenuineIntel
Prozessorfamilie:  6
Modell:58
Modellname:Intel(R) Core(TM) i3-3227U CPU @ 1.90GHz
Stepping:  9
CPU MHz:   1800.000
Maximale Taktfrequenz der CPU:1901,
Minimale Taktfrequenz der CPU:779,
BogoMIPS:  3791.43
Virtualisierung:   VT-x
L1d Cache: 32K
L1i Cache: 32K
L2 Cache:  256K
L3 Cache:  3072K
Markierungen:  fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp 
lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf 
eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c lahf_lm ida 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep 
erms xsaveopt

unquote 

> 
> If you do:
> 
> cat > test.c << EOF
> #include 
> int main() { printf( "Testing\n"); }
> EOF
> 
> gcc -o testing test.c
> 
> ./testing
> 
> Does it work?
> 

Works perfect !

Ken: "I think you will need to rebuild gmp" The only way I see for doing it 
would be chrooting from the working partition. But I muss confess, that I am 
not sure how to do it. Do I need to go through the procedure as indicated in 
the lfs-book or would the chroot command of chapter 6 do the job ?

Bruce and Ken, thanks for the help !
Edgar
--- 
Dr.-Ing. Edgar Alwers 
GPG Key ID:AD5C6F70
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Ken Moffat]

On Mon, Feb 01, 2016 at 11:14:40PM +0100, Dr.-Ing. Edgar Alwers wrote:
> On Monday 01 February 2016 11:47:39 Bruce Dubbs wrote:
> 
> > 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.
> 
> I can only give the result for the laptop, as I am far from my PC:
> quote
> 
> Architektur:   i686
> CPU Operationsmodus:   32-bit, 64-bit
> Byte-Reihenfolge:  Little Endian
> CPU(s):4
> Liste der Online-CPU(s):0-3
> Thread(s) pro Kern:2
> Kern(e) pro Socket:2
> Sockel:1
> Anbieterkennung:   GenuineIntel
> Prozessorfamilie:  6
> Modell:58
> Modellname:Intel(R) Core(TM) i3-3227U CPU @ 1.90GHz

From something I learnt the other day, -3 intel CPUs are Ivy Bridge.
So, if the machine where you originally built is -4 or later then
gmp is probably the problem.  But if not, probably a different
problem.  If it _is_ a different problem, I would try memtest86 or
memtest86+ to check the laptop.

[...]
> 
> > 
> > If you do:
> > 
> > cat > test.c << EOF
> > #include 
> > int main() { printf( "Testing\n"); }
> > EOF
> > 
> > gcc -o testing test.c
> > 
> > ./testing
> > 
> > Does it work?
> > 
> 
> Works perfect !
> 
> Ken: "I think you will need to rebuild gmp" The only way I see for doing it 
> would be chrooting from the working partition. But I muss confess, that I am 
> not sure how to do it. Do I need to go through the procedure as indicated in 
> the lfs-book or would the chroot command of chapter 6 do the job ?
> 
> Bruce and Ken, thanks for the help !
> Edgar

I guess that chroot, with /proc, /sys, /dev mounted, should do it -
but I haven't had to try this.

ĸ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

Re: [blfs-support] Internal compiler error ?

[Dr.-Ing. Edgar Alwers]

On Monday 01 February 2016 17:30:56 Bruce Dubbs wrote:

> Try just rebuilding gmp:

Hmm, that is now a big problem. If I boot the new BLFS system, configure does 
not work, as I explained. 

And if I start using the old partition as host and change the root to the new 
BLFS system with  "chroot",  the configure of the new BLFS system will be used 
instead the working one from my host system. No way.

I would need a chroot but using the build systems of the host.  Is that 
possible ?

Thanks in advance,
Edgar
-- 
Dr.-Ing. Edgar Alwers 
GPG Key ID:AD5C6F70
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Bruce Dubbs]

Dr.-Ing. Edgar Alwers wrote:

On Monday 01 February 2016 17:30:56 Bruce Dubbs wrote:


Try just rebuilding gmp:


Hmm, that is now a big problem. If I boot the new BLFS system, configure does
not work, as I explained.

And if I start using the old partition as host and change the root to the new
BLFS system with  "chroot",  the configure of the new BLFS system will be used
instead the working one from my host system. No way.

I would need a chroot but using the build systems of the host.  Is that
possible ?


Try figuring out where configure is giving the problem and comment that 
part out.  It's jsut a bash script.


  -- Bruce


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-support] Internal compiler error ?

[Bruce Dubbs]

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"

2.) building e.g. "automoc4" "cmake -DCMAKE_INSTALL_PREFIX=/usr" works and
generates the files in "build". But when I enter "make", the program crashes
with an error:

"/opt/qt4/include/QtCore/qglobal.h:1315:1: internal Compiler-Error:
machinecode not valid. Please include the complete backtrace with any bug
report."

I do not understand this, as the only difference I see seems to be the
hardware. Has anyone experienced a similar problem ? I am asking for a hint,
what could be the reason of this problem ?
Included is a file with the output of the make process.


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 
int main() { printf( "Testing\n"); }
EOF

gcc -o testing test.c

./testing

Does it work?

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page