[lkml]   [2001]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectDHCP comiling issues under sparc linux
Below is the end of a thread between myself and Ted Lemon
regarding building DHCP under Sparc Linux.

I'm not well versed in parsing the kernel code to know
what the subtle differences in the different implementations
of this IOCtl, and am looking for some guidance from the
appropriate maintainers.

Please read below for the summary. I'll be happy to fill
in the blanks off-list.


-----Original Message-----
Ted Lemon responds to:
> Leif Sawyer who wrote:
> Under Kernel 2.4.3, at least for Sparc64, the following
> define in includes/cf/linux.h creates the problem:
> undef'ing this out allows the server to build correctly
> and initialize properly.
> #if !(defined(__sparc__) && (LINUX_MAJOR >= 2 && LINUX_MINOR >= 4))
> #endif

Hm. So Linux 2.4 on Sparc provides a different API than Linux 2.4 on
Intel. That's lame.

But I would like to think that this would be considered a bug, and
therefore fixed.

> I'll try this on my i386 box at home and see if it compiles correctly
> as well. That won't be until late tonight, if i'm lucky.

Cool, thanks. The code *should* work unmodified on Linux 2.4/i386.
Really, it should work for the sparc version as well - I don't suppose
I could talk you into reporting this to the Linux/sparc people as a

The deal is that you're supposed to be able to call SIOCGIFCONF with a
length of zero, and SIOCGIFCONF will return the length of the buffer
needed to record all the interface configuration information, and then
you allocate a buffer that size and call SIOCGIFCONF again. This
supposedly works on 2.4 for intel, and on 2.2 for intel, so it makes
sense that it should work on 2.2 and 2.4 for sparc as well. :'}

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.080 / U:1.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site