Slashdot Mirror


User: cheter

cheter's activity in the archive.

Stories
0
Comments
2
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 2

  1. 2.2.0 won't compile - GCC screwed ? on Linux 2.2 Released · · Score: 1

    All right. I figured that was a possibility, yeah. So, I "downclocked" my system to what the processor supposed to run (P150), and yeehaw, it compiled just nice and dandy.

    Then to problem #2, that happened right after I did the normal "post-compiling-kernel-steps". When it boots with the new kernel, I get the following message (just about):

    kernel panic: uable to load root system VFS on 03:00.

    Now, how do I get around THIS ??

  2. 2.2.0 won't compile - GCC screwed ? on Linux 2.2 Released · · Score: 1

    Hi folks.

    When I try to compile the new kernel I get the following error:

    gcc: Internal compiler error: program cc1 got fatal signal 11
    make[3]: *** [floppy.o] Error 1
    make[3]: Leaving directory `/usr/src/linux-2.2.0/drivers/block'
    make[2]: *** [first_rule] Error 2
    make[2]: Leaving directory `/usr/src/linux-2.2.0/drivers/block'
    make[1]: *** [_subdir_block] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.2.0/drivers'
    make: *** [_dir_drivers] Error 2
    [root@otherland linux]# cpp: output pipe has been closed

    ...

    What's this supposed to mean ? I get it in various places...

    I'm too unsmart to understand why this happens