From owner-freebsd-gnome Tue Feb 18 16:37:25 2003 Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C853337B401; Tue, 18 Feb 2003 16:37:23 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-52.dsl.lsan03.pacbell.net [63.207.60.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F28F43FB1; Tue, 18 Feb 2003 16:37:23 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id B512F679DC; Tue, 18 Feb 2003 16:37:22 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id A01DC1198; Tue, 18 Feb 2003 16:37:22 -0800 (PST) Date: Tue, 18 Feb 2003 16:37:22 -0800 From: Kris Kennaway To: Juli Mallett Cc: Kris Kennaway , gnome@FreeBSD.ORG Subject: Re: gtk-sharp broken Message-ID: <20030219003722.GB50962@rot13.obsecurity.org> References: <20030218182554.GL97131@rot13.obsecurity.org> <20030218145715.A15780@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <20030218145715.A15780@FreeBSD.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 18, 2003 at 02:57:15PM -0600, Juli Mallett wrote: > * De: Kris Kennaway [ Data: 2003-02-18 ] > [ Subjecte: gtk-sharp broken ] > > http://bento.freebsd.org/errorlogs/i386-5-latest/gtk-sharp-0.7_1.log > >=20 > > It's possible this error is related to building in a jail (but I'd > > still like to understand it better). >=20 > I'd like to understand it better, too. Unfortunately, I don't :/ Is the= re > anything else exotic about the Bento build environment which might tickle > such a bug? I've yet to see a user complain, and I know I've pointed a > number of people to said port, who explicitly had no problem :( Well, as mentioned it could be because of the jail (e.g. the port is doing something that is disallowed or behaves differently in the jail). This current build run is the first time I've done that. Kris --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+UtHBWry0BWjoQKURAiVEAJsH/sKzrW0W24koRSpUkASDsp0HMACgqqsj VaodS7/TAcKZADsSTICspDY= =oNV3 -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message