[OpenAFS-devel] Re: Building OpenAFS on SmartOS

[chas williams - CONTRACTOR]

On Thu, 15 May 2014 01:28:22 -0400
Coy Hile <coy.hile@coyhile.com> wrote:

>         /home/hile/openafs/lib/libafscp.a ../../src/rxkad/liboafs_rxkad.la ../../src/fsint/liboafs_fsint.la ../../src/vlserver/liboafs_vldb.la ../../src/cmd/liboafs_cmd.la ../../src/util/liboafs_util.la ../../src/opr/liboafs_opr.la \
>         -lafshcrypto -lrokenafs -lpthread -lresolv  -lsocket -lnsl -lintl -ldl -lresolv  -lsocket -lnsl -lintl -ldl \

I think your problem is these bare -lintl which will wind up finding
the 32-bit version.

I suppose a way to fix this on 32-bit builds would give to make
-L/opt/local/lib happen earlier.

> Is there any way that one can short-circuit and build only the kernel modules (libafs64.o and libafs64.nonfs.o)?  It seems a waste when I eventually submodule the right bits into my own SmartOS platform build to build the entirety of the user land, just to throw it all away since it won’t ship in the image anyhow.

try running 'make libafs'