Trouble building gnomeprint...

[Jeremy Messenger]

On Sat, 25 Feb 2006 11:45:57 -0600, Jeremy Messenger <mezz7 at cox.net> wrote:

> On Sat, 25 Feb 2006 11:30:11 -0600, Eric Schuele  
> <e.schuele at computer.org> wrote:
>
>> Donald J. O'Neill wrote:
>>> 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
>
> Here, it should be -lglib-12, more comments below.

Umm, I mean -lgtk-12.

>>>>>>>> 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 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.
>>>>
>>>> Kris
>>>  What a regular portupgrade is to one can mean different things to  
>>> someone else.
>>
>> FWIW (if it helps diagnose the issue):
>> I said 'regular', meaning the same way I always do (`portupgrade -arR`,  
>>   with success), and with same frequency (weekly'ish).
>
> I don't think the 'portupgrade -a' or 'portupgrade -arR' will working  
> unless you use -fa together to get everything rebuild. I would do  
> 'portupgrade -afr' or something like that. As for your gnomeprint  
> problem, I checked in pointyhat and your log and it looks like you need  
> to reinstall gtk12 and possible other dependencies. The pointyhat has  
> -lgtk-12, -lgdk-12, and etc correct.
>
> http://pointyhat.freebsd.org/errorlogs/i386-6-latest-logs/gnomeprint-0.37_2.log
>
> In the /usr/ports/UPDATING said:
> ==============================================
> 20060223:
>    AFFECTS: all ports using libtool as part of the build process
>    AUTHOR: ade at FreeBSD.org
>
>    [...]
>
>    Unfortunately, there is no simple upgrade path.  Short of removing
>    all packages and reinstalling from scratch, the only other viable
>    alternative would be careful use of portupgrade. [....]
> ==============================================
>
> My plan of this afternoon is to remove all packages and reinstall from  
> scratch to get the better result.
>
> Cheers,
> Mezz
>
>>> 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 too have gtk12.  Never had any problems till this.
>>
>>> 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


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org