Re: why should kernel headers care about glibc versions?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi ...

On Feb 18, 2008 2:11 AM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
>
> in the header file include/linux/scoket.h, we see the test:
>
>   #if defined(__KERNEL__) || !defined(__GLIBC__) || (__GLIBC__ < 2)

Hm, IMHO, if defined(__KERNEL__) is true (for kernel code), do we
really need to care of the rest of conditions?

Or...if it's used for user space, that means (again ..IMHO) it can be
used with provided glibc. So, I guess it has to be used with "custom"
library...just like what kernel code does (by providing its own
library).

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux