Re: net/openafs fails on FreeBSD-10.3 (afs_sysnames.h not updated)

Thanks for the report, and my apologies for committing the incomplete fix;
I guess it needed to get more review in upstream's gerrit than it got.

I'll be travelling for the next week, though, so I don't expect to be able
to get the proper fix in very soon, unfortunately.

-Ben

On Fri, 27 May 2016, Jan Henrik Sylvester wrote:

> On FreeBSD-10.3, I tried to build the net/openafs port you updated a few
> hours ago. It failed due to SYS_NAME_ID_amd64_fbsd_103 not being declared.
>
> With the patch attached, the port builds and the AFS works.
>
> Trying to update afs_sysnames.h correctly, I wondered about IDs being
> used more than once:
>
> SYS_NAME_ID_i386_fbsd_45=SYS_NAME_ID_i386_fbsd_46=2103
> SYS_NAME_ID_i386_fbsd_72=SYS_NAME_ID_i386_fbsd_100=2130
> SYS_NAME_ID_i386_fbsd_73=SYS_NAME_ID_i386_fbsd_101=2131
> SYS_NAME_ID_amd64_fbsd_72=SYS_NAME_ID_amd64_fbsd_100=3030
> SYS_NAME_ID_amd64_fbsd_73=SYS_NAME_ID_amd64_fbsd_101=3031
>
> Considering 4.5 and 4.6 the same might have been correct, but 7.2 is
> 10.0 and 7.3 is 10.1 -- weird.
>
> Anyhow for 10.2 and 10.3, I used the next free number above the two for
> 10.1.
>
> Cheers,
> Jan Henrik
>