Date: Fri, 15 Oct 2004 13:37:06 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Emanuel Strobl <Emanuel.Strobl@gmx.net> Cc: freebsd-current@freebsd.org Subject: Re: xterm (+Konsole) and su on BETA4 with Xorg (from today) Message-ID: <20041015203706.GA92908@xor.obsecurity.org> In-Reply-To: <200409140338.12764.Emanuel.Strobl@gmx.net> References: <200409140338.12764.Emanuel.Strobl@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 14, 2004 at 03:38:07AM +0200, Emanuel Strobl wrote: > Hello, >=20 > attention: perhaps a stupid question, but probably a big problem: >=20 > When I su (without -l) I'm not able to build any port. I get the followin= g=20 > error message (e. g.): >=20 >=20 > cale:/usr/ports/security/cryptplug# make > =3D=3D=3D> Vulnerability check disabled, database not found > =3D=3D=3D> Extracting for cryptplug-0.3.16_1 > >> Checksum OK for cryptplug-0.3.16.tar.gz. > =3D=3D=3D> Patching for cryptplug-0.3.16_1 > =3D=3D=3D> cryptplug-0.3.16_1 depends on executable: gpgme-config - fo > =3D=3D=3D> cryptplug-0.3.16_1 depends on executable: gpg-agent - found > =3D=3D=3D> cryptplug-0.3.16_1 depends on executable: gmake - found > =3D=3D=3D> cryptplug-0.3.16_1 depends on file: /usr/local/bin/libtool1 > =3D=3D=3D> Configuring for cryptplug-0.3.16_1 > cp: /usr/ports/security/cryptplug/work/cryptplug-0.3.16 > /usr/ports/security/cryptplug/work/cryptplug-0.3.16/config.guess:=20 > r directory > *** Error code 1 >=20 > Stop in /usr/ports/security/cryptplug. >=20 >=20 > When I su with "-l" it's no problem to build that port. This is _not_ spe= cific=20 > to cryptoplug at all. Any port fails if I don't "su -l"! >=20 > I'm really "stoned". I upgraded from BETA3 to BETA4 (on newfs'd labels, s= o=20 > actually it's a reinstall, not a upgrade!) with freshly built ports (KDE3= .3,=20 > formerly KDE3.2.3 but always xorg with nvidia-drivers) I think this was a bug in kdm that was recently fixed - can you please verify that you have completely up-to-date ports? Kris --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBcDTyWry0BWjoQKURAgIpAKC5BZ7MeekYt4XDT/Az+CErnS7PxwCcCP9I gVE4X93bI6l1d5oPgHvGUX0= =zTkq -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041015203706.GA92908>