If you have xfree86, I dunno, but xorg will fail running some
programs if you don't restart the build (xclock, gvim, etc.)
If you rebuild everything, I bet fc-cache will work for you as well.
xorg does not modify the fonts AFAICT, it just bombs on some of them.
For that reason, I'm betting that you'll have odd failures with other
programs you build as well.
On Mon, 17 Apr 2006, null null wrote:
Hisashi T Fujinaka <htodd <at> twofifty.com> writes:
On Tue, 11 Apr 2006, Dylan wrote:
FWIW, running fc-cache -v shows segfaults on
/Library/Fonts and
/System/Library/Fonts. Temporarily moving these
(e.g. to Fonts.old) allows xorg
to complete installation (while, obviously,
missing those fonts). Perhaps
fc-cache is just choking on one of these? I
unfortunately won't have a chance to
do more investigation for a while.
This is all on an Intel MacBook. Building
everything from source. xorg now runs
as expected, though I don't know what the
implications of moving the fonts
around are.
Did anyone reply to this? I've only done a couple of
experiments and I
think you have several choices:
1) delete all of X and X dependencies and rebuild
everything from
scratch. Don't use the bindist. This is what you
need to do if you want
xorg or xfree86. You'll have failures with random X
apps otherwise.
2) delete xorg and everything you've compiled for X
since you installed
xorg, and install Apple's X11 and the X11 SDK. With
this option, you can
use the bindist (something that Debian-ish users
usually like).
Option 1 means no bindist. Option 2 means bindist is
OK. Option 1 is
"gentoo-ish", option 2 is "Debian-ish." :)
I suppose. But the .debs get built one way or the
other, which should be fine for any Debian user :) I,
personally, am completely sorted now. I had taken
option 1 above successfully. But I only completed that
after shuffling the directories as noted.
The real question for me is: are /Library/Fonts and
/System/Library/Fonts modified by xorg? I think not.
In xorg's postinst, after everything compiled from
scratch as per option 1, fc-cache died on those (or
rather, the fonts in those) directories. When those
were temporarily moved out of the way, fc-cache (as
part of the installation of the xorg .deb) completed
properly.
Anyway, like I said, I:
a) have a (seemingly) perfectly functioning X (in
fact, I have successfully gone with both 1 and 2 above
at different times)
b) I don't remember the specifics at the moment, but
xorg wouldn't complete postinst (because of fc-cache
crashing) with /{,System/}Library/Fonts available.
I'd file a bug, but want to figure out a bit better
what's causing fc-cache to die first. Anyway, I'll
look into it further when I get a chance (it's my
girlfriend's MacBook; I'm just trying to make it more
familiar to *me* when I get a chance to log in, thus
the slowness in my information-gathering :)
Anyway, thanks for the reply. Maybe this is helpful to
someone trying to get xorg running. I'm going to try
to figure out what fc-cache doesn't like; it could be
just this particular machine.
Dylan
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
Hisashi T Fujinaka - [EMAIL PROTECTED]
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
