compilation failure of 2.2 series cvs kernel sources

compilation failure of 2.2 series cvs kernel sources

[Satadru Pramanik]

After getting the sources with "cvs update -dP -rlinux_2_2"
 I use the enclosed file as my .config, and then run a "make vmlinux"  The
only change I made was to line 455 of linux/net/ipv4/ip_options.c,
deleting "kfree_skb(skb);"  to fix the DOS attack on the 2.2 series
kernels recently found.  

Any output would be appreciated.  Thanks.  I have a egcs 1.1.2 system.

here's the dying output of the compile:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -D__powerpc__ -fsigned-char
-msoft-float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple
-mstring   -c -o scsi.o scsi.c
scsi.c: In function `scan_scsis_single':
scsi.c:768: `TYPE_ENCLOSURE' undeclared (first use in this function)
scsi.c:768: (Each undeclared identifier is reported only once
scsi.c:768: for each function it appears in.)
scsi.c: In function `resize_dma_pool':
scsi.c:2499: `TYPE_ENCLOSURE' undeclared (first use in this function)
make[3]: *** [scsi.o] Error 1
make[3]: Leaving directory `/usr/src/linux/drivers/scsi'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/drivers/scsi'
make[1]: *** [_subdir_scsi] Error 2
make[1]: Leaving directory `/usr/src/linux/drivers'
make: *** [_dir_drivers] Error 2

Thanks again.


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: compilation failure of 2.2 series cvs kernel sources

[Martin Costabel]

Satadru Pramanik wrote:
> 
> After getting the sources with "cvs update -dP -rlinux_2_2"
>  I use the enclosed file as my .config, and then run a "make vmlinux"  The
> only change I made was to line 455 of linux/net/ipv4/ip_options.c,
> deleting "kfree_skb(skb);"  to fix the DOS attack on the 2.2 series
> kernels recently found.
> 
> Any output would be appreciated.  Thanks.  I have a egcs 1.1.2 system.
> 
> here's the dying output of the compile:
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -D__powerpc__ -fsigned-char
> -msoft-float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple
> -mstring   -c -o scsi.o scsi.c
> scsi.c: In function `scan_scsis_single':
> scsi.c:768: `TYPE_ENCLOSURE' undeclared (first use in this function)

Just a wild guess: Did you upgrade your glibc-devel recently? 

TYPE_ENCLOSURE is defined in /usr/src/linux/include/scsi/scsi.h.
Formerly, /usr/include/scsi/ was a symlink to
/usr/src/linux/include/scsi/. It is now owned by glibc which has its own
scsi.h file without this definition. It happened to me that upgrading
glibc overwrote the contents of /usr/src/linux/include/scsi, with
disastrous results. Why there is such a directory in glibc is beyond me;
these *are* kernel headers, after all.

--
Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: compilation failure of 2.2 series cvs kernel sources

[satadru pramanik]

yes. I did upgrade glibc recently. ;-)

However, the symlink is still the same.   Do I need to change it?  And
wouldn't doing a cvs update change the scsi.h file "back"?  Or is that the
problem?

On Wed, 2 Jun 1999, Martin Costabel wrote:

Satadru Pramanik wrote:
> 
> After getting the sources with "cvs update -dP -rlinux_2_2"
>  I use the enclosed file as my .config, and then run a "make vmlinux"  The
> only change I made was to line 455 of linux/net/ipv4/ip_options.c,
> deleting "kfree_skb(skb);"  to fix the DOS attack on the 2.2 series
> kernels recently found.
> 
> Any output would be appreciated.  Thanks.  I have a egcs 1.1.2 system.
> 
> here's the dying output of the compile:
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -D__powerpc__ -fsigned-char
> -msoft-float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple
> -mstring   -c -o scsi.o scsi.c
> scsi.c: In function `scan_scsis_single':
> scsi.c:768: `TYPE_ENCLOSURE' undeclared (first use in this function)

Just a wild guess: Did you upgrade your glibc-devel recently? 

TYPE_ENCLOSURE is defined in /usr/src/linux/include/scsi/scsi.h.
Formerly, /usr/include/scsi/ was a symlink to
/usr/src/linux/include/scsi/. It is now owned by glibc which has its own
scsi.h file without this definition. It happened to me that upgrading
glibc overwrote the contents of /usr/src/linux/include/scsi, with
disastrous results. Why there is such a directory in glibc is beyond me;
these *are* kernel headers, after all.

--
Martin



----
satadru pramanik `satadru@umich.edu'
"Put your hand on a hot stove for a minute, and it seems like an hour. Sit
with a pretty girl for an hour, and it seems like a minute. THAT'S
relativity." 
-Albert Einstein
---


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: compilation failure of 2.2 series cvs kernel sources

[Martin Costabel]

satadru pramanik wrote:
> 
> yes. I did upgrade glibc recently. ;-)
> 
> However, the symlink is still the same.   Do I need to change it?  And
> wouldn't doing a cvs update change the scsi.h file "back"?  Or is that the
> problem?

I don't really know what happens in this case, but it shouldn't be hard
to find out what version of include/scsi/scsi.h (and sg.h, which sits in
the same boat) you have: "cvs status include/scsi/scsi.h".
BTW, cvs log tells me that TYPE_ENCLOSURE came into scsi.h on February
9, version 1.10.

--
Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]