error in compilation kernel 2.6.19 - internal compiler error

error in compilation kernel 2.6.19 - internal compiler error

[Thibaud Hulin]

Hello !

I'm triyng to compile the kernel 2.6.19 on Debian Testing 4.0
Unfortunately, I can't success.
This is my error message :

CC [M]  drivers/scsi/lpfc/lpfc_sli.o
In file included from drivers/scsi/lpfc/lpfc_sli.c:23:
include/linux/pci.h:251: internal compiler error: in build_int_cst_wide, 
at tree.c:803
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[4]: *** [drivers/scsi/lpfc/lpfc_sli.o] Erreur 1
make[3]: *** [drivers/scsi/lpfc] Erreur 2
make[2]: *** [drivers/scsi] Erreur 2
make[1]: *** [drivers] Erreur 2
make[1]: quittant le répertoire « /home/hulin/src_hitachi/linux-2.6.19 »
make: *** [debian/stamp-build-kernel] Erreur 2


Thanks for help,
Thibaud.

Re: error in compilation kernel 2.6.19 - internal compiler error

[Paolo Ornati]

On Sat, 24 Mar 2007 16:45:46 +0100
Thibaud Hulin <hulin.thibaud@wanadoo.fr> wrote:

> I'm triyng to compile the kernel 2.6.19 on Debian Testing 4.0
> Unfortunately, I can't success.
> This is my error message :
> 
> CC [M]  drivers/scsi/lpfc/lpfc_sli.o
> In file included from drivers/scsi/lpfc/lpfc_sli.c:23:
> include/linux/pci.h:251: internal compiler error: in build_int_cst_wide, 
> at tree.c:803
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> For Debian GNU/Linux specific bug reporting instructions,
> see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
> The bug is not reproducible, so it is likely a hardware or OS problem.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Have you read the error message?

It could be a memory problem (defective module)... try run memtest86 or
memtest86+ (http://www.memtest.org/) for many hours (>= 8, someone
suggest even 24h, just to be sure :).

If the problem is big memtest should find it soon.

-- 
	Paolo Ornati
	Linux 2.6.20.4 on x86_64