Trouble building gnomeprint...

[Eric Schuele]

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/libgnomeprint'
>>>>> 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 at 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.

Maybe something got out of whack on my machine.  Seems I noticed that 
libtool needed attention, it mentioned "stale origins".  Then within a 
day or so, libtool got bumped.  So I did a portupgrade and it upgraded. 
  Then many of my ports needed upgrading (used `portupgrade -arR`).  So 
this is what I was in the middle of when that error occurred.  Many 
(most?) got upgraded fine.  I'm left with nine or so that are blocking 
on this error.

Anything I can do to get past it?

> 
> Kris
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 


-- 
Regards,
Eric