From owner-freebsd-gnome Thu Feb 14 7: 7:34 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from omega.lovett.com (omega.lovett.com [209.249.90.123]) by hub.freebsd.org (Postfix) with ESMTP id B691637B405; Thu, 14 Feb 2002 07:07:29 -0800 (PST) Received: from [24.243.55.247] (helo=[10.0.0.2] ident=ident) by omega.lovett.com with asmtp (Exim 3.33 #1) id 16bNTn-000CqB-00; Thu, 14 Feb 2002 07:07:24 -0800 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Thu, 14 Feb 2002 09:08:28 -0600 Subject: Re: Problem building ports/x11/gnome From: Ade Lovett To: , Cc: , Message-ID: In-Reply-To: <20020214113141.A856737B402@hub.freebsd.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit 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 On 02/14/02 05:31, "Mathias.Picker@virtual-earth.de" wrote: > > > On 14 Feb, Thyer, Matthew wrote: >> The problem is in the build of ports/x11/gnomelibs >> >> Looks like the configure test program is not linking with >> the installed imlib-1.9.11 (which the ports system correctly >> installed as a dependency). >> >> Everything on my machine is build from ports on a very recent >> -CURRENT. > > I can second that. The only other thing that I found out is that > imlib_config dumps core....?? Sadly, I do not have the time to > investigate further. I suggest that you both re-read freebsd-current, paying particular attention to issues with the link-loader, causing a variety of problems, such as this. This is not a ports issue, it's a -current issue, that I believe is now fixed (so you'll have to update your OS). -aDe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message