[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Compiling 2.4.0-test12




a few weeks ago i've the same problem ... compiling a module of the kernel
(some modules related to the network drivers (3com and RealTek, AFAIR))
and it sends an "Internal compiler error in function sparc_emit_set_const32"

the problem was on the 3com module, b'cos it has some code that the 
compiler doesn't like, and then, crash, bing, booom ....... you know the
rest ...

that day i wrote:
     > i've tried with 2.2.15 from a deb package and 2.2.16 from ftp.kernel.org

and they told me:
     None will work. This wont be resolved until gcc3 makes it into woody, and
     we start using it to compile kernels.

maybe the SCSI module that you've choose has the same (kind of) code ...

try with other module wich "looks" like the one you are trying ... 

bye,
esteban

On Fri, 29 Dec 2000, RG wrote:

> Esteban,
> thank you for your prompt reply.
> I will try the "kernel-package".
> 
> In the meanwhile I tried to compile
> the 2.4.0-test12 but I have these troubles:
> 
> 1-putting these supports:
> SCSI device --->  SCSI low-level drivers  ---> Qlogic ISP SCSI support
> SCSI device --->  SCSI low-level drivers  ---> Qlogic ISP FC SCSI support
> I received:
> 
> sparc64-linux-gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test12/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -m64 -pipe -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -fcall-used-g5 -fcall-used-g7 -Wno-sign-compare -Wa,--undeclared-regs    -c -o qlogicfc.o qlogicfc.c
> ../../gcc/config/sparc/sparc.c:1174: Internal compiler error in function sparc_emit_set_const32
> cpp: output pipe has been closed
> make[3]: *** [qlogicfc.o] Error 1
> 
> 2-getting rid off the supports above I received, in the last phases of compiling:
> 
> ld -m elf64_sparc -T arch/sparc64/vmlinux.lds arch/sparc64/kernel/head.o arch/sparc64/kernel/init_task.o init/main.o init/version.o \
>         --start-group \
>         arch/sparc64/kernel/kernel.o arch/sparc64/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/sparc64/math-emu/math-emu.o \
>         drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/parport/parport.a  drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/cdrom.a drivers/pci/pci.a drivers/sbus/sbus_all.o drivers/video/video.o \
>         net/network.o \
>         /usr/src/linux-2.4.0-test12/lib/lib.a /usr/src/linux-2.4.0-test12/lib/lib.a /usr/src/linux-2.4.0-test12/arch/sparc64/prom/promlib.a /usr/src/linux-2.4.0-test12/arch/sparc64/lib/lib.a \
>         --end-group \
>         -o vmlinux
> drivers/video/video.o(.data.init+0x8): undefined reference to `sbusfb_init'
> drivers/video/video.o(.data.init+0x10): undefined reference to `sbusfb_setup'
> make: *** [vmlinux] Error 1
> 
> Any ideas?
> Could anyone suggest to me the usual SCSI driver to put support into the kernel for a standard Ultra5?
> Thank you in advance.
> 
> Roberto Giorgetti.
> 
> 
> On Thu, Dec 28, 2000 at 02:35:05PM -0300 or thereabouts, Esteban Osses A.  Mag. 2000 wrote:
> > 
> > 
> > On Thu, 28 Dec 2000, RG wrote:
> > 
> > > [sorry, i don't know about cd burners ...]
> > > 
> > > By the way, I am now compiling the kernel
> > > (thank you for answer to my previous question: egcs64)
> > > the usual commands:
> > 
> > ... but about the kernel, try to use "kernel-package" ... it contains some 
> > scripts to compile a new kernel and generate a .deb package with the new 
> > kernel and the modules ...
> > 
> > bye,
> > esteban
> > 
> > 
> > > 
> > > make bzImage
> > > 
> > > or
> > > 
> > > make zImage
> > > 
> > > are not valid, what have I to make?
> > > 
> > > What is the SCSI adapter tipically inside an Ultra 5?
> > > Which kind of SCSI support I should put in the kernel?
> > > 
> > > Thank you for your patience.
> > > 
> > > Roberto Giorgetti.
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 







Reply to: