Re: why should kernel headers care about glibc versions?

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

 



Hi,

"Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx> writes:

>> 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?

No these are ORs.  If the header is included from the kernel itself, not
from glibc or from a glibc that is older than version 2, the definitions
are visible.

This seems like a backward-compatibility stuff for definitions that have
moved to glibc by now but not on older versions.

	Hannes


--
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