compiling kernel errors(slack1.1.2.15)

compiling kernel errors(slack1.1.2.15)

Post by Mark Smi » Fri, 11 Mar 1994 15:16:12



Help?  I've been trying to compile the Linux kernel for awhile now..
I just ftped Slackware 1.1.2p15 from sunsite.unc.edu this last weekend
(3/5/94)..  When I installed, the kernel didn't come with ethernet
support, so I have to compile it in.  But I continually
get a signal 11 from cc1:

gcc: Internal compiler error: program cc1 got fatal signal 11

I know this is a segfault, but the strange thing is that it rarely
ever happens in the same place twice..  This is my setup:

        486DX-25MHz  (Yes, it's an old chip)
        8MGs RAM
        16MGs swap space
        164MG root partition
        50MG /home partition
        3com503 10BaseT Ethernet card
        Slackware 1.1.2 with kernel .99p15 running
        gcc 2.5.8
        include v4.5.19 (according to the install program)

I reinstalled the D series from floppy and the same thing happens..
Am I using something wrong here?  Any help would be appricated.. THank
you for your time.


---
Mark Smith                      | The Halibut BBS               ___ O    

KD6JTS                          | Cal Poly in SLO TOWN!      |/\___/        
--------------------------------+--------------------------------------------
        "Why won't Windows work on my Macintosh?"
                - The ultimate DFO error
Mark Smith                      | The Halibut BBS               ___ O    

KD6JTS                          | Cal Poly in SLO TOWN!      |/\___/        
--------------------------------+--------------------------------------------

 
 
 

compiling kernel errors(slack1.1.2.15)

Post by Grant Edwar » Sat, 12 Mar 1994 04:37:09


: Help?  I've been trying to compile the Linux kernel for awhile now..
: I just ftped Slackware 1.1.2p15 from sunsite.unc.edu this last weekend
: (3/5/94)..  When I installed, the kernel didn't come with ethernet
: support, so I have to compile it in.  But I continually
: get a signal 11 from cc1:

: gcc: Internal compiler error: program cc1 got fatal signal 11

: I know this is a segfault, but the strange thing is that it rarely
: ever happens in the same place twice..  This is my setup:

The sig 11 problem is usually blamed on hardware problems.  It seems
to happen at random during kernel builds particularly.  Unfortunately,
the hardware problems that people report are many and varied.  People
have claimed that they solved the signal 11 problem by:

  + replacing a SIMM
  + replacing the disk controller
  + slowing down the ISA bus
  + replacing the motherboard or CPU board.

The last one is what I had to do. :( I tried the exact same
installation (disk controller, video board, disks, SIMMs, bus-board)
with a different CPU board.  One CPU board had the problem, the other
didn't.

Some have claimed it happens only when swapping is going on, others
say differently.

If anybody has any more definitive answers please let me know!

--
Grant Edwards                                 |Yow!  I wish I was a
Rosemount Inc.                                |sex-starved manicurist found
                                              |dead in the Bronx!!


 
 
 

compiling kernel errors(slack1.1.2.15)

Post by Tony Poo » Sun, 13 Mar 1994 11:04:10



>The sig 11 problem is usually blamed on hardware problems.  It seems
>to happen at random during kernel builds particularly.  Unfortunately,
>the hardware problems that people report are many and varied.  People
>have claimed that they solved the signal 11 problem by:

[list deleted]

There is another reason you don't list, but I don't know what it is.  I
posted about a week ago with about the same problem that Mark is
experiencing without any help offered.  Strangely enough, my seg faults
happen in exactly the same places with exactly the same set of programs.
Trying to compile the kernel, dosemu, f2c, etc give me signal 11's, while
xfm, xpm, xview, pico, and a few others worked fine.  I even had xfm, xpm,
and xview compiling all at once, using all 8 meg of ram, and about 5 to 8
meg of swap.  Worked fine to completion.

I wish someone could suggest SOMETHING to check.

It's not like it's a random thing - I could handle that.
--

------------------------------------------------------------------------------