From owner-freebsd-ports@FreeBSD.ORG Sat Feb 25 15:04:37 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F272616A422 for ; Sat, 25 Feb 2006 15:04:36 +0000 (GMT) (envelope-from duncan.fbsd@gmail.com) Received: from smtp113.sbc.mail.re2.yahoo.com (smtp113.sbc.mail.re2.yahoo.com [68.142.229.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F8E243D48 for ; Sat, 25 Feb 2006 15:04:36 +0000 (GMT) (envelope-from duncan.fbsd@gmail.com) Received: (qmail 6497 invoked from network); 25 Feb 2006 15:04:35 -0000 Received: from unknown (HELO pres1750.mylan.net) (donaldj@ameritech.net@69.211.89.144 with plain) by smtp113.sbc.mail.re2.yahoo.com with SMTP; 25 Feb 2006 15:04:35 -0000 From: "Donald J. O'Neill" To: Kris Kennaway Date: Sat, 25 Feb 2006 09:04:23 -0600 User-Agent: KMail/1.9.1 References: <43FFDB8F.1000703@computer.org> <200602250811.17053.duncan.fbsd@gmail.com> <20060225141918.GA95617@xor.obsecurity.org> In-Reply-To: <20060225141918.GA95617@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602250904.23687.duncan.fbsd@gmail.com> Cc: freebsd-ports@freebsd.org, Eric Schuele Subject: Re: Trouble building gnomeprint... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2006 15:04:37 -0000 On Saturday 25 February 2006 08:19, Kris Kennaway wrote: > On Sat, Feb 25, 2006 at 08:11:16AM -0600, Donald J. O'Neill wrote: > > On Saturday 25 February 2006 08:03, Eric Schuele wrote: > > > Kris Kennaway wrote: > > > > On Fri, Feb 24, 2006 at 10:22:39PM -0600, Eric Schuele wrote: > > > >> During a regular portupgrade, I ran into the following: > > > >> > > > >> /usr/bin/ld: cannot find -lgtk12 > > > >> gmake[2]: *** [libgnomeprint.la] Error 1 > > > >> gmake[2]: Leaving directory > > > >> `/usr/ports/print/gnomeprint/work/gnome-print-0.37/libgnomepri > > > >>nt' gmake[1]: *** [all-recursive] Error 1 > > > >> gmake[1]: Leaving directory > > > >> `/usr/ports/print/gnomeprint/work/gnome-print-0.37' > > > >> gmake: *** [all-recursive-am] Error 2 > > > >> *** Error code 2 > > > >> > > > >> Stop in /usr/ports/print/gnomeprint. > > > >> ** Command failed [exit code 1]: /usr/bin/script -qa > > > >> /tmp/portupgrade90656.30 make > > > >> ** Fix the problem and try again. > > > >> > > > >> I've done some looking around. Not sure how to fix it. Looks > > > >> like it can't find gtk12? So I deinstalled/reinstalled it, > > > >> and rebuilt pkgdb. No go. Am I way off base here? What am I > > > >> missing? > > > > > > > > /usr/ports/UPDATING; you need to portupgrade -a or equivalent. > > > > > > > > Kris > > > > > > I generally use `portupgrade -arR`. This is how I ran into the > > > problem. Tried just `portupgrade -a` as well, with the same > > > results. > > > > > > Any other way (besides removing all ports, and reinstalling)? > > > > > > Thanks. > > > > Hi Eric, > > > > possibly Kris was trying to refer you to this from > > /usr/ports/UPGRADING: > > > > 20051105: > > AFFECTS: all users of gnome/glib/gtk > > AUTHOR: gnome@FreeBSD.org > > > > GNOME has been updated to 2.12 and gtk/glib to 2.8. > > DO NOT USE portupgrade(1) to update your ports. Instead, use > > the gnome_upgrade.sh script from > > http://www.marcuscom.com/downloads/gnome_upgrade212.sh > > > > Any possibility of this? > > No, the libtool entry. > > Kris What a regular portupgrade is to one can mean different things to someone else. It might be "Hey that's excessive time between upgrades," and it might be "Why are you doing it so often?" It depends. Did Eric do the upgrade to gnome2.12 in November or December, or is he just catching it now with all the rest. I've got gtk12 on my systems and didn't have a problem with the libtool upgrade. I didn't like it too much after waiting for 36 hours for one big upgrade to complete and then being hit with the libtool upgrade two days later which took about, I forget, I don't care, I got through it without problems. Don