[OpenAFS-devel] Building OpenAFS on SmartOS

[coy.hile@coyhile.com]

Did anything ever come of that change that Adam Glasgall mentioned? I haven'=
t seen any other mention of him clicking around hyperlinks in gerrit.

Sent from my iPhone

> On May 3, 2014, at 16:33, "Chas Williams (CONTRACTOR)" <chas@cmf.nrl.navy.=
mil> wrote:
>=20
> I wrote this a bit back.  It supports everything but the kernel.
> There appears to be some header confusion and I couldn't see the gcc
> options that were necessary.  But I only needed userspace so...
>=20
> http://gerrit.openafs.org/#change,10464
>=20
> Since the other commenter said he had something to do this already I
> abandoned this change.
>=20
> In message <84B1FFFB-308B-4081-B144-58EC5BC73FB4@coyhile.com>,Coy Hile wri=
tes:
>> Good afternoon, all.
>>=20
>> I=3D92m working on getting OpenAFS to build on SmartOS.  SmartOS builds =3D=

>> completely with gcc these days (unlike, perhaps, other bits bits of the =3D=

>> greater illumos/Solaris ecosystem.  However, the Solaris-specific bits =3D=

>> of the source tree assume that one will be using the Studio compilers =3D=

>> exclusively.  I=3D92ve got two questions. =3D20
>>=20
>> Firstly, is there any guide or best practice for converting a makefile =3D=

>> between supporting the Studio compilers and gcc?  So far, I=3D92ve figure=
d =3D
>> out that -KPIC in CFLAGS becomes -fPIC, and that there=3D92s no -mt optio=
n =3D
>> to gcc. =3D20
>>=20
>> The second is perhaps of more use; what is the consensus about doing the =3D=

>> changes to autoconf=3D92d bits to support gcc if on SmartOS?  Would case =3D=

>> statements for =3D93joyent=3D94 in uname -v output be the best way to =3D=

>> differentiate between SmartOS and everybody else who still uses studio?  =3D=

>> If I can get the first question sorted, I can certainly get something =3D=

>> that will work; the question is whether a local patch that I keep around =3D=

>> in my own repos, or if it=3D92s something the larger community would like=
 =3D
>> to see contributed back.
>>=20
>> Thanks,
>>=20
>> -c=3D
>> _______________________________________________
>> OpenAFS-devel mailing list
>> OpenAFS-devel@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-devel
>>=20