From owner-freebsd-questions Fri Nov 29 8: 1:49 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3988E37B414 for ; Fri, 29 Nov 2002 08:01:45 -0800 (PST) Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A38043EC2 for ; Fri, 29 Nov 2002 08:01:44 -0800 (PST) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.physik.uni-mainz.de (klima.physik.uni-mainz.de [134.93.180.162]) by klima.physik.uni-mainz.de (8.12.6/8.12.5) with ESMTP id gATG1ggw094471 for ; Fri, 29 Nov 2002 17:01:42 +0100 (CET) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Fri, 29 Nov 2002 17:01:42 +0100 (CET) From: "Hartmann, O." To: freebsd-questions@freebsd.org Subject: Kerberos IV/Heimdal breaks PicoBSD?? Message-ID: <20021129164326.O94128-100000@klima.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello. I aesked this question before and I try to ask it again. Since I enabled Kerberos IV __and__ Heimdal together to be built in /etc/make.conf, it is no longer possible to compile PicoBSD. Not only our own config is affected, all default configs have also this problem. This is the output of the picobsd built-process: bsd/bastion//usr/src/sbin/mount_cd9660/getmntopts.o crunchide -k _crunched_mount_cd9660_stub mount_cd9660.lo cc -static -o crunch1 crunch1.o init.lo fsck.lo ifconfig.lo sh.lo echo.lo pwd.lo mkdir.lo rmdir.lo chmod.lo chown.lo mv.lo ln.lo mount.lo minigzip.lo cp.lo rm.lo ls.lo kill.lo df.lo ps.lo ns.lo vm.lo cat.lo test.lo hostname.lo login.lo getty.lo stty.lo w.lo msg.lo kget.lo reboot.lo sysctl.lo swapon.lo pwd_mkdb.lo dev_mkdb.lo umount.lo mount_std.lo du.lo tail.lo tee.lo passwd.lo sleep.lo basename.lo expr.lo route.lo ee.lo arp.lo disklabel.lo fdisk.lo vnconfig.lo grep.lo date.lo mount_nfs.lo ping.lo ipfw.lo traceroute.lo mount_cd9660.lo -L/usr/lib -lncurses -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm -lmytinfo -lipx -lz -lpcap -lwrap -ltermcap -lgnuregex -lkrb5 -lkrb -ldes -lcom_err -lkadm5clnt -lkadm5srv -lssl -lkadm /usr/lib/libkadm.a(kadm_cli_wrap.o): In function `kadm_init_link': kadm_cli_wrap.o(.text+0x6c): undefined reference to `initialize_krb_error_table' kadm_cli_wrap.o(.text+0x368): undefined reference to `krb_net_write' kadm_cli_wrap.o(.text+0x383): undefined reference to `krb_net_write' kadm_cli_wrap.o(.text+0x39e): undefined reference to `krb_net_read' kadm_cli_wrap.o(.text+0x3f9): undefined reference to `krb_net_read' kadm_cli_wrap.o(.text+0x516): undefined reference to `krb_mk_priv' kadm_cli_wrap.o(.text+0x5a1): undefined reference to `des_quad_cksum' kadm_cli_wrap.o(.text+0x76f): undefined reference to `krb_rd_priv' /usr/lib/libkadm.a(kadm_stream.o): In function `stv_string': kadm_stream.o(.text+0x202): undefined reference to `strnlen' *** Error code 1 Stop in /usr/src/release/picobsd/build_dir-bastion/crunch. ---> fail: Error <1> error code in <> Error while building bastion. ---> Aborting /usr/src/release/picobsd/build/picobsd The base of our config is picobsd/bridge. The crunch.config has not been edited but the last line to include libs as they are reported to be missed by the built-process. The more libs I added, the more errors disappeared, but not all. Sorry for that unconvenience. Someone out here asked to get the config files but I lost his address (sorry). Hope someone has some solutions ... thanks. -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ------------------------------------------------------------------ IT-Administration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message