summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2005-05-27 12:25:42 +0000
committerrwatson <rwatson@FreeBSD.org>2005-05-27 12:25:42 +0000
commit46520b8295c838a99c47e75dfa43fe0ea7811bff (patch)
treed590bc0147396204d863d1e2cbaef479151f315b
parent194c67c3c8bad703f62d8f1294c11eb847764428 (diff)
downloadFreeBSD-src-46520b8295c838a99c47e75dfa43fe0ea7811bff.zip
FreeBSD-src-46520b8295c838a99c47e75dfa43fe0ea7811bff.tar.gz
Back out ipx.h:1.18, which introduced a Linux API compatibility field in
the ipx_net data structure. Doing so introduced a stronger alignment requirement for the address structure, which in turn propagated into other dependent data structures, which turns out not to be suported by the available IPX source code. As a result, a number of user space applications, such as IPX routing components, failed to operate correctly. RELENG_5_3 candidate? PRs: 74059, 80266 Pointy hat to: bms Fix by: bde Tested by: Keith White <Keith dot White at site dot uottawa dot ca> MFC after: 1 week Suffering: great
-rw-r--r--sys/netipx/ipx.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/netipx/ipx.h b/sys/netipx/ipx.h
index dc97d09..3331747 100644
--- a/sys/netipx/ipx.h
+++ b/sys/netipx/ipx.h
@@ -108,7 +108,6 @@ union ipx_host {
union ipx_net {
u_char c_net[4];
u_short s_net[2];
- u_int u_net;
};
union ipx_net_u {
@@ -132,8 +131,6 @@ struct sockaddr_ipx {
char sipx_zero[2];
};
#define sipx_port sipx_addr.x_port
-#define sipx_network sipx_addr.x_net.u_net
-#define sipx_node sipx_addr.x_host.c_host
/*
* Definitions for IPX Internetwork Packet Exchange Protocol
OpenPOWER on IntegriCloud