Yeah, make libafs alone on that particular image will do what I need. I'm going to stand up a fileserver running this code from master (commit cc215459) this afternoon/evening. I'll report back how it works.
Sent from my iPhone > On May 15, 2014, at 7:04, chas williams - CONTRACTOR <[email protected]> > wrote: > > On Thu, 15 May 2014 01:28:22 -0400 > Coy Hile <[email protected]> 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' > _______________________________________________ > OpenAFS-devel mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-devel :—§ TќzчҐ™ЁҐЉx%ЉЛNҐйА'^ЅйhҐйЪ~К+‚m¦Пя–+-ІЉ^ќ§мўё?™ЁҐ™©я–+-ЉwиюЉ^ќ§мuлЮ
