Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Feb 2000 20:18:56 -0500
From:      Walter Brameld <>
To:        Salvo Bartolotta <>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Re Complex interdependent [meta]ports (was Re: Gnome Install)
Message-ID:  <00022920343002.27246@Bozo_3.BozoLand.domain>
In-Reply-To: <>
References:  <00022818593701.00658@Bozo_3.BozoLand.domain> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Salvo! Good to hear from you again, seems like it's been a while.

I haven't gotten very far along these lines, being relatively new to
FreeBSD but it looks like you, myself and several others are running
into this problem. I had already taken the step of cd'ing to /usr/ports
and running 'make clean' as part of the answer. Yours does seem to be
the drastic solution, nuking the flies instead of swatting them. I took
the other approach, just dealing with the discrepancies as they

In the case of 'gnome', there were only two. I was rather pleased I was
able to deal with them not knowing that much about systems, but then
I've heard even a blind squirrel finds a nut once in a while...

I'm not sure what the optimal solution to this would be. As in my case,
why did the metaport say the libungif libraries were present when in
fact they were not?

I guess until someone comes up with a better answer I'll just keep
tripping over those nuts.

On Tue, 29 Feb 2000, in a never-ending search for enlightenment, Salvo
Bartolotta wrote: > >>>>>>>>>>>>>>>>>> Original Message
<<<<<<<<<<<<<<<<<< > 
> On 2/29/00, 12:38:58 AM, Walter Brameld <> wrote 
> regarding Gnome Install:
> > Was just curious if the person asking earlier was able to finally
> > install Gnome. I decided to try it just to see if it would work (Well
> > yes, as a matter of fact I AM bored!).
> > When it reached the point of installing gnomeprint, it failed with the
> > message "-lungif - no such file or directory". libungif was shown as a
> > dependancy and the install claimed it as "found" when in fact it was
> > not installed on my system.
> > Next stop: gmake[2] gave a failure when trying to compile parsef.c or
> > some such. This was cured by de-installing and installing gmake!
> > It just now finished (this sucker must download about 50 meg!) without
> > any further errors.
> > I don't do a lot of fiddling with my system, and I guess I'm just
> > curious as to how it could have gotten into this state. As for the
> > person installing gnome, watch the errors and do some back-checking.
> > Apparently some rather peculiar conditions can cause it to fail.
> >   --  Walter Brameld
> Dear Walter,
> Last week, I met (by and large) analogous problems when dealing with 
> such mega "metaports". I tried to install KDE11-i18n-1.1.2, just to 
> play with Russian etc. locales in a more "international" fashion (or, 
> if you prefer, "context").
> The first installation produced no (apparent) errors; however, 
> KDE-i18n did NOT operate properly. The next day, I cvsupped the ports 
> tree , and installed (again, as a port) the new version of qt-i18n 
> (1.44b) -- after making clean and pkg_deleting the previous version of 
> that toolkit.  
> The remedy was worse than the disease.
> A moment's thought suggested a drastic but effective solution:
> i) suitably grep e.g. the metaport installation log, extracting the 
> directories of the ports as well as the packages installed; of course, 
> you can also directly obtain the dependency list via the ports 
> mechanism (pretty-print-build-depends-list target ...); 
> ii) create a simple script pkg_deleting -f **all** of the KDE-related 
> packages, and cleaning the corresponding ports (ie issuing "make 
> clean" in their directories);
> iii) reinstall the KDE11-i18n port.
> Needless to say, it behaves well enough now -- although it took its 
> time to compile and install. Incidentally, the Japanese locale is 
> somehow slow on my PIII 450 Mhz 384 MB RAM -- probably (?) because of 
> the time it takes to draw Japanese "pictures"; on the other hand, the 
> Russian locale (ya gavaryoo pa-rooskee ;-) , which is much more 
> responsive, takes a little time to open, say, a 2MB HTML file.    
> I seem to understand that, when such complex dependencies are 
> involved, an updated [meta]port may imply overall interwoven 
> (interrelated) modifications: simply pkg_deleting and remaking the 
> port for *just* one package in the [meta]port, in general, may NOT 
> work. Those modifications are only included if you rebuild **all** of 
> the relevant [meta]port components.
> Unless I have completely misunderstood it, and I have made an awful 
> blunder ...  
> Best regards
> Salvo
Walter Brameld

n. Someone who has been educated past his/her level of intelligence.
Join the Army, meet interesting people, kill them.

To Unsubscribe: send mail to
with "unsubscribe freebsd-questions" in the body of the message

Want to link to this message? Use this URL: <>