From: ghod@drycas.club.cc.cmu.edu Subject: Re: 0.99pl10 won't compile with TCP/IP configured Date: 10 Jun 1993 01:34:16 -0400
In article <STEVEV.93Jun9194228@miser.uoregon.edu>, stevev@miser.uoregon.edu
(Steve VanDevender) writes:
> Here's more information (and a much more descriptive subject
> line) about the problem I'm having.
[stuff about setting up compiler and preliminary kernel deleted]
> I first ran into a problem with limits.h during the "make dep"
> phase. After grepping through most of the recent posts to
> c.o.l., I found one answer which said that commenting out the
> line "#include_next <limits.h>" seemed to fix the problem.
This is indeed the correct thing to do. I'm not sure what exactly is broken,
but getting rid of that statement will make things sane again. (I #ifdefed
it out of the way muself.) I presume that this 'gotcha', like all the others,
will be fixed in short order.
> Then I found that the in.h supplied with the libc.so.4.4 release
> appears to conflict with the kernel's in.h. Here are the error
> messages GCC gives:
>
> gcc -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -fomit-frame-pointer -DD_LINK_IO=0x378 -DD_LINK_IRQ=
> 7 -UD_LINK_DEBUG -c d_link.c -o d_link.o
> In file included from /usr/include/netinet/in.h:94, from d_link.c:88:
> /usr/include/linux/in.h:24: conflicting types for `IPPROTO_IP'
> /usr/include/netinet/in.h:30: previous declaration of `IPPROTO_IP'
[etc etc...]
> make[2]: *** [d_link.o] Error 1
Holy deja-vu Batman! I ran into this same problem. The trouble is that
/usr/include/netinet/in.h is out of date/incompatible with the new kernel.
/usr/include/linux/in.h is the file you want to use since it comes with
the kernel sources to begin with. What I did was to get rid of
/usr/include/netinet/in.h and replace it with a symbolic link to
/usr/include/linux/in.h. Alternatively, you could just replace it
with a file that just says: #include <linux/in.h>. I believe that
/usr/include/netinet/tcp.h should get the same treatment.
> If I configure the kernel without TCP/IP, I can get it to
> compile, but the unix-domain sockets don't seem to agree with X.
> Starting X usually gives me a blank screen, then hangs such that
> VC switching or attempting to kill the server with
> CTRL-ALT-Backspace doesn't work at all.
Can't help you here except to say fix the previous two problems and compile
with TCP/IP enabled. :)
> --
> Steve VanDevender stevev@greylady.uoregon.edu
Hope this helps.
-Bill Paul
ghod@drycas.club.cc.cmu.edu