>That's exactly what I'm doing now: that will be tedious enough as I
>re-run configure 10 times and spell out exactly where qt and friends are

...huh?  Just use pkgsrc; type ``make update'' in the appropriate
directory and let it go.

I haven't manually configured/ported/compiled more than about 3 to 6
pieces of software since starting to use NetBSD.  pkgsrc makes it *so*
easy to compile things semi-automatically.  (^&

(The things that I've compiled are a couple of versions of Regina (a REXX
implementation), an LPMud driver or two, and DrScheme (before we had a
package for it).)

Everything else, I compile from pkgsrc.  I am on *very* poor speaking
terms with configure/autoconf/automake/etc.  I never used them on my
Amiga, and (almost) never needed to use them on NetBSD.


I think that you (Paul) were using pkgsrc.  Linda was trying to avoid that
by using precompiled binaries.

Dunno about your build problems...try using CVS to grab pkgsrc from the
first week in December and try that.  That worked for me, without any real
problems.



(I should probably amend a previous comment: KDE has mostly worked for me.
I seem to recall some oddities---e.g., with kdevelop---but I only lightly
used it to see what was there.  I can't remember much by way of specific
problems, so it may have worked better than I recall.  I think that audio
support and screen-blankers didn't work with it at a time when GNOME was
supporting those (admittedly, that's a minor point).  I never could figure
out kdevelop's GUI-editor, either; dunno if that was pilot error, poor
design, or software bugs.  I have the vague feeling that there were more
concrete, serious things, but that may be ``mental fuzz'' coming from the
``It's big; it doesn't work perfectly'' aspect, and not a real memory.)


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu