I'm investigating porting the OVS code (well, at least the userspace
portions) to Solaris. On my first stab, I immediately ran into a couple
of issues,
1 - lib/byte-order.h defines htonll and ntohll inline functions which
are already defined as macros on Solaris resulting in compile time errors.
2 - lib/flow.c references a structure ip6_ext that is defined in OVS in
netinet/ip6.h. However, Solaris has its own version of netinet/ip6.h
which supersedes the one
included by OVS.
I can certainly think of ways of working around these issues. However,
it was my hope that, once I ported to Solaris, the changes could be
incorporated
back into the base source. Given that the OVS source has already been
ported to FreeBSD and NetBSD, I assume issues like this have been
encountered.
Are there any general rules on how OS portability issues should be resolved?
Thanks,
Mark
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
