Re: [Linux-decnet-user] compiling 2.26 / ifconfig

[Patrick C. <pa...@ty...>]

On Wed, Jun 09, 2004 at 02:40:30PM +0100, Alex Finch wrote:
> 
>  I have a couple of problems with linux-decnet. It works ( version 2.23) - 
> however...
> 
> 
> 
> 1) Installing the decnet module stops ifconfig working:
> 
>    modprobe decnet
>    ifconfig
>    : error fetching interface information: Device not found
> 
> 
>      I also find that my nis-client will occasionally die, and I suspect it 
>      is also due to decnet, but I have not proved it.
> 
>  So far as I know I have got my kernel compiled correctly, .config contains
> 
> CONFIG_DECNET=m
> CONFIG_DECNET_SIOCGIFCONF=y

No, that's wrong. CONFIG_DECNET_SIOCGIFCONF should not be set. It causes exactly
the problem you've just seen
 
> 
>  2) I can not compile 2.26, it says:
> 
> 
> -- gcc -pipe -fdollars-in-identifiers -fsigned-char -Wstrict-prototypes 
> -Wall
> -Wno-unused -Wno-uninitialized -I../libdap -I../include -DVERSION=\"2.26\"
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSHADOW_PWD -DDNETUSE_DEVPTS -g 
> -Wl,-rpath-link,../libdnet -Wl,-rpath-link,../libdap -o example example.o 
> -L. -lrms
> ../libdap/libdap.so.2: undefined reference to `atexit'
> collect2: ld returned 1 exit status

I'm not sure why that should be, it compiles OK for me on a large number of Linux 
platforms. As that's only an example program for librms then it will be safe
to comment it out of the Makefile.

Which distribution & version are you using ?

>  3) Why is it not possible to remove the decnet module?

Because it would cause a memory leak. The neighbour table cleanup routines are 
incomplete in 2.4. I'm not sure of the exact details though.

patrick