I have tried to compile 1.6.10 on OS X 10.10.

The first problem is that it will not compile with xcode 5 or 6. I have not
checked if there is a way to change the compiler to gcc on xcode 6, so it
might be possible (the command gcc starts c-lang).

I compiled it on an MacOS 10.9 system that had an older Xcode. That binary
works if I remove the OS version checks in the install script and disable
signature checks with sudo nvram boot-args="kext-dev-mode=1". kext-dev-mode
is of course not recommended for normal usage.

10.10 requires all kernel extensions to be signed. They ship a list of
hashes for old kernel extensions, that is why some versions of openafs will
work on an upgraded system. But new openafs versions have to be signed.

I have not been able to sign my kernel extension as I just discovered that
I have to apply for rights to sign kernel extensions. A normal developer
certificate is not enough. I don't know how long that process will take.


The conclusion is that there is probably a bit of code cleaning that has to
be done in the long term. To just get things to work someone have to get
the releases signed.



On Wed, Oct 8, 2014 at 3:41 PM, Jan Iven <jan.i...@cern.ch> wrote:

> Our Mac support was wondering whether MacOS 10.10 will run OpenAFS.
> Perhaps somebody has some experiences to share (apparently 10.9 needed a
> new openafs-1.6.6 release before becoming installable)?
> Of course, in the end we will need to do our own tests, but if the answer
> is "don't bother, needs a new release again" this might wait..
>
> Google says other people might be interested as well, these look like
> status pages being built (but without openafs info so far):
>
> * http://kb.mit.edu/confluence/display/istcontrib/OS+X+
> Yosemite++%2810.10%29+BETA+Known+Issues
> * http://oithelp.nd.edu/applications-and-operating-systems/mac-os-x/
>
> Thanks in advance
> jan
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

Reply via email to