fontconfig 2.2.0 on -stable

[Mike Hoskins]

On Tue, 22 Apr 2003, Joe Marcus Clarke wrote:
> Strange.  If you search the mailing list archives for the errors you're
> seeing, you'll see '.' was historically the cause.  What is your $PATH
> right before running make install (note, some shells may expand the
> current working directory from '.' to something like
> "/usr/ports/print/freetype2")?  In fact, I just did:

I'd read that FAQ, but having admin'd UNIX for ~10 years now I'm one of
those who avidly preach against having '.' in PATH.  :)  However, it did
seem to be related to PATH, so your diagnosis was basicly correct...

I had simply done 'su' then began the install.  That left me with my PATH,
which while not containing '.' is more inclusive than root's.

My path:

PATH=:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/home/mike/bin

After your suggestion, I simply hit ctrl-d and did 'su -' which gave me
root's path (still no '.', but more stripped down):

Root's path:

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin

After the 'su -' freetype2 installed.  Odd, no?  Maybe it's something to
do with how my path is built up in my .profile vs. the default root
.profile.  I do it somewhat round-a-bout, but haven't noticed it causing
problems before,

PATH=""; export PATH
for i in { /bin /sbin /usr/bin /usr/sbin \
           /usr/local/bin /usr/local/sbin \
           /usr/X11R6/bin /usr/local/samba/bin $HOME/bin }
do
        if [ -d $i ]; then
                PATH=$PATH:$i
                export PATH
        fi
done

The good news is I've sorted through most of the brokeness thanks to your
help sorting out freetype2.  (After that a few other problems went away
too, including GTK2 and Pango.)

Now I'm rebuilding the latest 1.3 Mozilla from ports...  I tried
installing the 1.2 binary package, but noticed it has an ORBit2 dependancy
that 1.3 from ports doesn't seem to have.  ORBit2 seems to die here (from
ports) because libIDL-2.0 isn't installed.  The odd thing is I don't see
any mention of libIDL >= 0.8.0_1 in ports, despite the 1.2 Mozilla package
seeming to require it.  (?)  So back to the 1.3 build and praying...

> Maxim is on the GNOME team.  We "share" freetype2 responsibilities
> sometimes since it's so tightly integrated with GNOME.

Well, thanks for the help...  Most of the time portupgrade just works for
me and I don't have many questions...  From time to time, however, things
seem to really break in ways I don't quite manage to comprehend.  :)

-mrh

--
From: "Spam Catcher" <spam-catcher at adept.org>
To: spam-catcher at adept.org
Do NOT send email to the address listed above or
you will be added to a blacklist!