[OpenAFS] Building 1.8.2 with transarc-paths
Prasad K. Dharmasena
pkd@umd.edu
Thu, 15 Nov 2018 18:21:39 -0500
--000000000000a55a22057abc5160
Content-Type: text/plain; charset="UTF-8"
Thanks, Mike and Ben, for the tips.
I decided to try building it with the '--enable-static --disable-shared'
options first, and that works.
We have been using AFS since (pre-IBM) Transarc days, so a lot of our
deployment/upgrade scripts rely on those paths. I was just trying to find
the quickest way to upgrade to the 1.8.x series w/o having to make too many
changes. Yes, I think, it is time to abandon the transarc paths.
On Sat, Nov 10, 2018 at 9:25 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
> On Thu, Nov 08, 2018 at 04:27:09PM -0500, Michael Meffie wrote:
> > On Wed, 7 Nov 2018 21:41:06 -0500
> > "Prasad K. Dharmasena" <pkd@umd.edu> wrote:
> >
> > > I've been building 1.6.x on Ubuntu 16.04 with the following options
> and it
> > > has worked well for me.
> > >
> > > --enable-transarc-paths
> > > --prefix=/usr/afsws
> > > --enable-supergroups
> > >
> > > Building 1.8.x on the same OS with the same option has a problem that
> > > appears to be an rpath issue.
> > >
> > > ldd /usr/vice/etc/afsd | grep not
> > > libafshcrypto.so.2 => not found
> > > librokenafs.so.2 => not found
> > >
> > > Those libraries are installed in /usr/afsws/lib, so I can get the
> client to
> > > run if I set the LD_LIBRARY_PATH. Any hints to what I need to tweak in
> > > 'configure' to make it build properly?
> > >
> > > Thanks.
> >
> > Hello Prasad,
> >
> > OpenAFS 1.8.x introduced those two shared object libraries. When not
> installing
> > from packages you'll need to run ldconfig or set the LD_LIBRARY_PATH.
> Since
> > you've copied the files to /usr/afsws/lib, you can create a ldconfig
> configuration
> > file to let it know where to find them. For example,
> >
> > $ cat /etc/ld.so.conf.d/openafs.conf
> > /usr/afsws/lib
> >
> > or perphaps better, install them to a standard location recognized by
> ldconfig.
>
> I might also ask why you are using the transarc paths at all -- wouldn't it
> be easier to conform to the de facto standard filesystem hierarchy with the
> default openafs configuration?
>
> (There's also the option of passing --enable-static --disable-shared to
> configure, though I don't remember exactly what that ends up doing.)
>
> Thanks,
> Ben
>
--000000000000a55a22057abc5160
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif">Thanks, Mike and Ben, for the tips.</d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif">I decided to try building it with the '--enable-stat=
ic --disable-shared' options first, and that works.=C2=A0=C2=A0</div><d=
iv class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"=
><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetic=
a,sans-serif">We have been using AFS since (pre-IBM) Transarc days, so a lo=
t of our deployment/upgrade scripts rely on those paths.=C2=A0 I was just t=
rying to find the quickest way to upgrade to the 1.8.x series w/o having to=
make too many changes.=C2=A0 Yes, I think, it is time to abandon the trans=
arc paths.=C2=A0=C2=A0</div><div class=3D"gmail_default" style=3D"font-fami=
ly:arial,helvetica,sans-serif"><br></div></div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr">On Sat, Nov 10, 2018 at 9:25 AM Benjamin Kaduk &l=
t;<a href=3D"mailto:kaduk@mit.edu">kaduk@mit.edu</a>> wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">On Thu, Nov 08, 2018 at 04:27:09PM -0500, Mich=
ael Meffie wrote:<br>
> On Wed, 7 Nov 2018 21:41:06 -0500<br>
> "Prasad K. Dharmasena" <<a href=3D"mailto:pkd@umd.edu" ta=
rget=3D"_blank">pkd@umd.edu</a>> wrote:<br>
> <br>
> > I've been building 1.6.x on Ubuntu 16.04 with the following o=
ptions and it<br>
> > has worked well for me.<br>
> > <br>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--enable-transarc-paths<br>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--prefix=3D/usr/afsws<br>
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--enable-supergroups<br>
> > <br>
> > Building 1.8.x on the same OS with the same option has a problem =
that<br>
> > appears to be an rpath issue.<br>
> > <br>
> > ldd /usr/vice/etc/afsd | grep not<br>
> > libafshcrypto.so.2 =3D> not found<br>
> > librokenafs.so.2 =3D> not found<br>
> > <br>
> > Those libraries are installed in /usr/afsws/lib, so I can get the=
client to<br>
> > run if I set the LD_LIBRARY_PATH.=C2=A0 Any hints to what I need =
to tweak in<br>
> > 'configure' to make it build properly?<br>
> > <br>
> > Thanks.<br>
> <br>
> Hello Prasad,<br>
> <br>
> OpenAFS 1.8.x introduced those two shared object libraries. When not i=
nstalling<br>
> from packages you'll need to run ldconfig or set the LD_LIBRARY_PA=
TH. Since<br>
> you've copied the files to /usr/afsws/lib, you can create a ldconf=
ig configuration<br>
> file to let it know where to find them. For example,<br>
> <br>
>=C2=A0 =C2=A0 =C2=A0$ cat /etc/ld.so.conf.d/openafs.conf <br>
>=C2=A0 =C2=A0 =C2=A0/usr/afsws/lib<br>
> <br>
> or perphaps better, install them to a standard location recognized by =
ldconfig.<br>
<br>
I might also ask why you are using the transarc paths at all -- wouldn'=
t it<br>
be easier to conform to the de facto standard filesystem hierarchy with the=
<br>
default openafs configuration?<br>
<br>
(There's also the option of passing --enable-static --disable-shared to=
<br>
configure, though I don't remember exactly what that ends up doing.)<br=
>
<br>
Thanks,<br>
Ben<br>
</blockquote></div>
--000000000000a55a22057abc5160--