[11/12] kbuild: Use POSIX headers for ntoh functions

From: Sam Ravnborg
Date: Fri Aug 13 2004 - 15:05:43 EST


# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/08/10 22:11:50+02:00 sam@xxxxxxxxxxxxxxxxx
# kbuild: Use POSIX headers for ntoh functions
#
# From: Benno <benjl@xxxxxxxxxxxxxxx>
# When compiling Linux on Mac OSX I had trouble with scripts/sumversion.c.
# It includes <netinet/in.h> to obtain to definitions of htonl and ntohl.
#
# On Mac OSX these are found in <arpa/inet.h>. After checking the POSIX
# specification it appears that this is the correct place to get
# the definitons for these functions.
#
# (http://www.opengroup.org/onlinepubs/009695399/functions/htonl.html)
#
# Using this header also appears to work on Linux (at least with
# Glibc-2.3.2).
#
# It seems clearer to me to go with the POSIX standard than implementing
# #if __APPLE__ style macros, but if such an approach is preferred I can
# supply patches for that instead.
#
# Signed-off-by: Sam Ravnborg <sam@xxxxxxxxxxxx>
#
# scripts/mod/sumversion.c
# 2004/08/10 22:11:33+02:00 sam@xxxxxxxxxxxxxxxxx +1 -1
# Use correct POSIX header for ntoh functions
#
# scripts/basic/fixdep.c
# 2004/08/10 22:11:33+02:00 sam@xxxxxxxxxxxxxxxxx +1 -1
# Use correct POSIX header for ntoh functions
#
diff -Nru a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
--- a/scripts/basic/fixdep.c 2004-08-13 21:07:40 +02:00
+++ b/scripts/basic/fixdep.c 2004-08-13 21:07:40 +02:00
@@ -104,7 +104,7 @@
#include <stdio.h>
#include <limits.h>
#include <ctype.h>
-#include <netinet/in.h>
+#include <arpa/inet.h>

#define INT_CONF ntohl(0x434f4e46)
#define INT_ONFI ntohl(0x4f4e4649)
diff -Nru a/scripts/mod/sumversion.c b/scripts/mod/sumversion.c
--- a/scripts/mod/sumversion.c 2004-08-13 21:07:40 +02:00
+++ b/scripts/mod/sumversion.c 2004-08-13 21:07:40 +02:00
@@ -1,4 +1,4 @@
-#include <netinet/in.h>
+#include <arpa/inet.h>
#include <stdint.h>
#include <ctype.h>
#include <errno.h>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/