Error compiling linux22

Christian Stueble stueble at amaunet.cs.uni-dortmund.de
Sat Oct 9 14:32:48 CEST 1999


Hi again,

thanks for your replies.

I changed nothing on my system and I get (another) errors if I use only
8MB. Currently the compiler likes the following error (-:
----
ld: Warning: size of symbol `' changed from 49 to 4 in sys.o
ld: Warning: type of symbol `' changed from 2 to 1 in sys.o
sys.o(.data+0x4): multiple definition of `'
signal.o(.data+0x0): first defined here
sys.o: In function `':
sys.o(.text+0x0): multiple definition of `'
signal.o(.data+0x0): first defined here
ld: Warning: size of symbol `' changed from 4 to 51 in sys.o
ld: Warning: type of symbol `' changed from 1 to 2 in sys.o
sys.o: In function `(0,3)=r(0,1);0020000000000;0017777777777;':
/sb/linux22/include/linux/sched.h(.text+0x34): multiple definition of `'
signal.o(.data+0x0): first defined here
sys.o: In function `(0,3)=r(0,1);0020000000000;0017777777777;':
r(0,23)(.text+0x68): multiple definition of `'
signal.o(.data+0x0): first defined here
ld: Warning: size of symbol `' changed from 51 to 6 in sys.o
make[2]: *** [kernel.o] Segmentation fault
-----

It seems to be a problem of my system:
I tried to compile a current linux kernel (2.2.12) and got the following
error:
-----
rm -f ipv4.o
ld -m elf_i386  -r -o ipv4.o  utils.o route.o proc.o timer.o protocol.o ip_input.o ip_fragment.o ip_forward.o ip_options.o ip_output.o ip_sockglue.o tcp.o tcp_input.o tcp_output.o tcp_timer.o tcp_ipv4.o raw.o udp.o arp.o icmp.o devinet.o af_inet.o igmp.o sysctl_net_ipv4.o fib_frontend.o fib_semantics.o fib_hash.o
ip_sockglue.o: file not recognized: File truncated
-----

This problem is not L4-related, I´ll be back if it works :-)

Ciao,
Christian



Am Sat, 09 Oct 1999 schrieben Sie:
> On Fri, 8 Oct 1999, Ramon van Handel wrote:
> 
> > >gcc: Internal compiler error: program cc1 got fatal signal 11
> > 
> > Are you overclocking ?
> > 
> > Otherwise, you probably have a bad SIMM.  You should read the GCC-SIG11 FAQ
> > that comes with every linux distro.
> > 
> > Ramon
> 
> My personal experience with this is that I had my RAM set to 60ns instead
> of 70ns (which makes gcc work).
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Christian Stueble............stueble at ls6.cs.uni-dortmund.de
 PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A

 To be or not to be is true...   (apocrypha of George Boole)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-              



More information about the l4-hackers mailing list