Re: Missing compile_et and kerberos breaks buildworld
--WfZ7S8PLGjBY9Voh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jan 15, 2013 at 04:46:01PM -0800, Steve Kargl wrote:
> > It actually gets quite worse from there.
>=20
> Yep. :(
> I just hit
>=20
> cc -O2 -pipe -march=3Dopteron -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD=
_ENVIRON -DENV_HACK -DSTREAMSPTY -DINET6 -I/usr/src/libexec/telnetd/../../=
contrib/telnet -DAUTHENTICATION -DENCRYPTION -DKRB5 -DFORWARD -Dnet_write=
=3Dtelnet_net_write -std=3Dgnu99 -Qunused-arguments -fstack-protector -Wsys=
tem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-s=
ign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unu=
sed-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -W=
no-switch -Wno-switch-enum -o telnetd global.o slc.o state.o sys_term.o te=
lnetd.o termstat.o utility.o authenc.o -lutil -ltermcap /usr/obj/usr/src/li=
bexec/telnetd/../../lib/libtelnet/libtelnet.a -lmp -lcrypto -lcrypt -lpam -=
lkrb5 -lhx509 -lasn1 -lroken -lcom_err
> /usr/obj/usr/src/tmp/usr/lib/libroken.so: undefined reference to `unvis@F=
BSD_1.0cc: error: linker command failed with exit code 1 (use -v to see inv=
ocation)
> *** [telnetd] Error code 1
>=20
This looks somewhat familiar.
I vaguely recall setting WITHOUT_TELNET to get past this.
Once buildworld finished successfully, I removed it from src.conf, and
things built afterwards.
> > I do not recall the details
> > off-hand, but I recall doing 'make obj all install' in somewhat this
> > order:
> >=20
> > - secure/
> > - include/
> > - kerberos5/
> > [some steps may be missing]
>=20
> Thanks for a possible roadmap. =20
>=20
I wish I had more useful details to provide. I'm going based on memory
at this point.
One other thing - make sure WITHOUT_GSSAPI (for ports) does not exist in
make.conf. That bit me on two of the three machines I went through this
nightmare.
Glen
PS: I thought I filed a PR with details on this, but it seems not to be
the case. :(
--WfZ7S8PLGjBY9Voh
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAEBCAAGBQJQ9fxCAAoJEFJPDDeguUajZsQH/3QJ+Lsqmz8BhjieO0SkVqS5
ovZWYfLk/XX0ouISvFakvAxUK8ETIEFiTf4kIcndc03wexWOHf1jNCDyWAGWZSfe
zaWoUAJUwJMIPQIqD30wkBRXTqFJHexMLk/fzIAWncZbyoPr+9YB6pQnnIu9covt
R1kY8BjZIHI/KDIUUJMOgf8SBBCMqjD0HNDfWai4IHE24OvsZ83D33eYcRKeAwnX
Q8R26hw++K897jzgtw2LK5QKzjTTkOWWweZCkgqB+Xu/1MS9DKoP6dXgpSAVXFHh
06FcKjdtFzorpi29L109dR77J8/YUg4xw3wRPcSuutuLrNUcgCb9t4hR0pGzWjs=
=dGe7
-----END PGP SIGNATURE-----
--WfZ7S8PLGjBY9Voh--
討論串 (同標題文章)
完整討論串 (本文為第 4 之 5 篇)：