> well, i'd like to know how far do we need to go. think of binary
> compatibility with 32/64/128/256bit CPUs, i believe we cannot do
> much here anyways.
>=> no, my concern is binary compatibility for the same 32 bit CPU with
>two different definitions of struct in6_addr.
maybe i wrongly assumed that you are talking about sparc64. i still
don't understand how generic your problem is...
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
- Re: [advanced API] how to get the destinatio... Francis Dupont
- Re: [advanced API] how to get the destination add... Tim Hartrick
- Re: [advanced API] how to get the destination add... Jun-ichiro itojun Hagino
- Re: [advanced API] how to get the destinatio... Erik Nordmark
- Re: [advanced API] how to get the destination add... Jun-ichiro itojun Hagino
- Re: [advanced API] how to get the destination add... Francis Dupont
- Re: [advanced API] how to get the destination add... Francis Dupont
- Re: [advanced API] how to get the destinatio... Erik Nordmark
- Re: [advanced API] how to get the destination add... itojun
- Re: [advanced API] how to get the destination add... Francis Dupont
- Re: [advanced API] how to get the destination add... Francis Dupont
- Re: [advanced API] how to get the destinatio... Jun-ichiro itojun Hagino
