On Thu, Jun 02, 2011 at 11:03:14AM -0700, Dan Fandrich wrote: > The only serious case I can think of that might break with this would be > alternate libcs on Linux, but given that most aim to be compatible with > glibc, which is it? If musl (or any others you're aware of) doesn't have > net/ethernet.h, I can add a clause in platform.h for it.
It has net/ethernet.h but not netpacket/packet.h. I suppose the latter could be added, but it would be nice if there were some attempt at making an agreement/mini-standard for what network headers should be used in modern code rather than having all this mess spread out over net, netinet, netpacket, arpa, etc. dirs with 25-75% redundancy and no good guidelines for modern usage. Rich _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
