Problem installing the MCC 172 HAT: "gcc: internal compiler error"

[danielt]

Hello all,

I tried to install the MCC 172 Hat on a new Raspberry Pi 4 B using the Install Instructions from Github (https://github.com/mccdaq/daqhats)

At step 7 "Build and install the shared library and tools. It will also detect the HAT board EEPROMs and save the contents, if needed." i get an error i can't solve by myself. 

sudo ./install.sh results in:

Building and installing library

make: Verzeichnis "/home/ama/daqhats/lib" wird betreten
gcc -I../include -I/opt/vc/include -I/usr/include -fPIC -Wall -Wextra -g -O2 -DENABLE_LOCALES=Off -MMD -c util.c -o build/util.o
gcc: internal compiler error: Ungültiger Maschinenbefehl signal terminated program cc1
Please submit a full bug report, with preprocessed source (by using -freport-bug).
See <file:///usr/share/doc/gcc-12/README.Bugs> for instructions.
make: *** [makefile:32: build/util.o] Fehler 4
make: Verzeichnis "/home/ama/daqhats/lib" wird verlassen
Library build failed
 

The MCC 172 is the only HAT installed (on top of the POE HAT), no jumpers for address 0 and the green light lights up constantly.

 

Can someone provide me any information how to fix this?

Greetings and thanks, Daniel

[DAQman]

Which version of Raspbian do you run?

What is the version of gcc installed?

Using the recommended power supply, you can try the process again without the POE hat.

[danielt]

14 hours ago, DAQman said:

Which version of Raspbian do you run?

What is the version of gcc installed?

Using the recommended power supply, you can try the process again without the POE hat.

Raspberry Pi 4 Model B Rev 1.5, 4GB

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

deb http://archive.raspberrypi.com/debian/ bookworm main

gcc (Debian 12.2.0-14) 12.2.0

 

I can't see how the POE-Hat should affect the function of the MCC 172, but if there is no other approach, i will try it without POE. 

[danielt]

20 hours ago, DAQman said:

Using the recommended power supply, you can try the process again without the POE hat.

Same error.

How can we proceed?

[DAQman]

The following is what I found online regarding the error you get:

The error 'killed signal terminated program cc1plus' typically occurs when a C++ compiler process (cc1plus) has been forcibly terminated by the system. This can happen for several reasons, including the system running out of memory, manually killing the process, or system-imposed resource limits triggering the termination of the process.

When compiling large projects or those with complex template use, the C++ compiler might consume significant amounts of memory. If the system deems that the compiler is using too much memory, it may issue a 'killed' signal to stop the compilation and release resources, resulting in the aforementioned error message. To resolve this issue, you may need to increase the amount of memory available to the compiler, close other resource-intensive applications

[danielt]

On 11/8/2024 at 6:05 PM, DAQman said:

The following is what I found online regarding the error you get:

The error 'killed signal terminated program cc1plus' typically occurs when a C++ compiler process (cc1plus) has been forcibly terminated by the system. This can happen for several reasons, including the system running out of memory, manually killing the process, or system-imposed resource limits triggering the termination of the process.

When compiling large projects or those with complex template use, the C++ compiler might consume significant amounts of memory. If the system deems that the compiler is using too much memory, it may issue a 'killed' signal to stop the compilation and release resources, resulting in the aforementioned error message. To resolve this issue, you may need to increase the amount of memory available to the compiler, close other resource-intensive applications

It is a Raspberry Pi 4 Model B Rev 1.5, 4GB, without any set up restrictions for the Ram usage. The MCC 172 HAT was build for the Raspberry Pi 4, right? So the 4 GB Version is the largest Pi 4 build, so i can't see how this could be a problem. I also use a 32 GB micro SD and except the Pi-OS. So in case there would be a need to assign more memory to a compiler, that would be part of the MCC 172 HAT manual, at least that's what I would expect.

 

So what can we do? Is there a possibility to check if the EEPROM is working? Is it possible to get a response to check the connection? Something like that? Could this be the problem?

Greetings, Daniel

[DAQman]

Could you let me know if you performed the recommended upgrade before attempting the daqhat installation?

sudo apt full-upgrade
sudo reboot

Is the util.c file the only one not compiling? 

Could you send me the install.sh output?

sudo ./install.sh >> text.txt

[danielt]

19 hours ago, DAQman said:

Could you let me know if you performed the recommended upgrade before attempting the daqhat installation?

sudo apt full-upgrade
sudo reboot

Is the util.c file the only one not compiling? 

Could you send me the install.sh output?

sudo ./install.sh >> text.txt

Yes, i followed the manual and did it 2 times to be sure.

This is the output-file (text.txt):

Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libqt5qmlworkerscript5 libqt5quickcontrols2-5 libqt5quicktemplates2-5
  qml-module-qtgraphicaleffects qml-module-qtquick-controls2
  qml-module-qtquick-layouts qml-module-qtquick-templates2
  qml-module-qtquick-window2 qml-module-qtquick2
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Building and installing library

make: Verzeichnis „/home/ama/daqhats/lib“ wird betreten
gcc -I../include -I/opt/vc/include -I/usr/include -fPIC -Wall -Wextra -g -O2 -DENABLE_LOCALES=Off -MMD -c util.c -o build/util.o
make: Verzeichnis „/home/ama/daqhats/lib“ wird verlassen
Library build failed

[danielt]

Quick feedback, i set up a new Raspberry Pi 4 with the same shiel, new OS Installation and so on and it seems to work.

I can't say what went wrong with the installation before, but now it seems to be fine.

Thanks

[DAQman]

It is good to hear you are up and running.

I wonder if the problem with the first RPI4 is the SD memory card.