rx/simple.example broken (Re: [OpenAFS-devel] IPv6 Status)

[Chas Williams (CONTRACTOR)]

this seems to build correctly on centos 6.2 with the 1_6_x branch.

besides changing sockaddr_in with sockaddr_in6 (although i would suggest
sockaddr_storage so someone can hopefully dual stack and/or future proof
against another network protocol)  you are going to need to fix the
host member in various rx structures.  this is used (among other things)
to demux the incoming packets into their appropriate rx calls.

In message <20120303192827.GH2874@excalibur.hozed.org>,Troy Benjegerdes writes:
>All righty then..
>
>(yells in Steven's direction)
>
>.. Why is this broken?
>
>hozer@six:~/src/openafs-v6-git/src/rx/simple.example$ make
>/home/hozer/src/openafs-v6-git/src/rxgen/rxgen -A -x -C -o sample.cs.c sample.xg
>gcc   -O   -I/home/hozer/src/openafs-v6-git/src/config -I/home/hozer/src/openafs-v6-git/include -I. -I.      -pthread -D_REENTRANT
> -DAFS_PTHREAD_ENV  -o sample.cs.o -c sample.cs.c
>sample.cs.c: In function ‘TEST_Add’:
>sample.cs.c:44: error: dereferencing pointer to incomplete type
>sample.cs.c:45: error: dereferencing pointer to incomplete type
>sample.cs.c: In function ‘TEST_Sub’:
>sample.cs.c:80: error: dereferencing pointer to incomplete type
>sample.cs.c:81: error: dereferencing pointer to incomplete type
>make: *** [sample.cs.o] Error 1
>
>
>I see the same problem in tests/auth as well.
>
>If I can do a brute-force search/replace of sockaddr_in with sockaddr_in6 
>and make rx/simple.example work, we have some code to start discussing
>other changes.
>
>(What I would also like to do is add an rx module for the NetPIPE benchmark,
>and then add and rx6 module once I have that working)
>
>We also had rxtcp at one point.. I don't see anything referencing that in
>the source tree, is hiding in plain sight someplace I missed?
>
>
>On Tue, Feb 28, 2012 at 01:08:46PM -0500, Steven Jenkins wrote:
>> On Tue, Feb 28, 2012 at 11:22 AM, Troy Benjegerdes <hozer@hozed.org> wrote:
>> ...
>> > If someone is sitting on a pile of code, or even a contract to do
>> > some IPv6 work, it would be nice to make a public timeline of when
>> > it will be available.
>> >
>> 
>> I am not sitting on a pile of code or documentations, and I do not
>> have a contract to do IPv6 work (although I, like many others, would
>> be open to doing so).
>> 
>> >
>> > If nothing else, can we at least get all the RPCs and APIs changes
>> > defined and documented?
>> 
>> Yell at me.  Frequently, personally, and loudly.  Seriously.  I've
>> volunteered to work on it before but not made any progress on it.  If
>> you (or someone else) were to ping me for updates, I'd prioritize it
>> higher than I do now (i.e., it's strictly a 'nice thing to do' project
>> for me so far).
>> 
>> Or if someone else wants to produce them, I'm fine with that, too.
>> 
>> Steven
>> _______________________________________________
>> OpenAFS-devel mailing list
>> OpenAFS-devel@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-devel
>
>-- 
>----------------------------------------------------------------------------
>Troy Benjegerdes                 'da hozer'                hozer@hozed.org  
>7 elements Farm						TerraCarbo biofuels
>
>If you're going through hell, keep going. ~ Winston Churchill
>
>The challenge in changing the world is not in having great ideas, it's in
>having stupid simple ideas, as those are the ones that cause change.
>