public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: type1 xorg module missing
Date: Sun, 15 Jun 2008 07:54:06 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.06.15.07.54.06@cox.net> (raw)
In-Reply-To: d257c3560806140807m6d5e3336vb4cd73bcd6fb9ad4@mail.gmail.com

Beso <givemesugarr@gmail.com> posted
d257c3560806140807m6d5e3336vb4cd73bcd6fb9ad4@mail.gmail.com, excerpted
below, on  Sat, 14 Jun 2008 15:07:28 +0000:

> 2008/6/14 Duncan <1i5t5.duncan@cox.net>:
> 
>> Beso <givemesugarr@gmail.com> posted
>> d257c3560806140630p28401537sd6ff45096a295f37@mail.gmail.com, excerpted
>> below, on  Sat, 14 Jun 2008 13:30:44 +0000:
>>
>> > i've gone with xorg-server--9999 and now i cannot find anymore the
>> > type1 extension. does anyone know to which package it belongs?!
>> > equery belongs doesn't help. is there some other way to find the
>> > package that provides a specific file?!
>>
>> $equery b libtype1.so
>> [ Searching for file(s) libtype1.so in *... ]
>> x11-base/xorg-server-1.4.0.90-r3
>> (/usr/lib64/xorg/modules/fonts/libtype1.so)
>> $
>>
> hmmm..... this is a little strange.... it seems like my xorg-server
> hasn't compiled it but nevertheless tries to load it at startup by
> default. i need to investigate a little what's the reason of this.

There doesn't appear to be a USE flag for it, so it's probably a hard-
wired part of the xorg-server build.  Only for some reason, your build 
for that library failed, and obviously, it's a non-fatal failure.

It's also possible you hit one of the bleeding edges of running a live 
sources ebuild.  Perhaps that's being split off into a separate package, 
but the dependencies aren't there yet, or there's a new USE flag I don't 
see in the 1.4.90-r3 version.

> ps. about the kernel build scripts you said you'd share are there any
> news?!

Thanks for the reminder.  I've been putting off upgrading to the latest 
kernel rc until I get the scripts spruced up a bit, after which the 
upgrade run would be the test to make sure that at least for here, I had 
it right.

The problem is that right now, there's some hard-coded paths and the 
like, that I'll need to change, "variablizing" them, with the settings 
preferably moved to a conf file, but at least all moved to the top of the 
scripts, where they're easy to see and set.

Looks like I might get some time 2nite to work on it, as it seems to have 
been a fairly slow newsgroups/mailinglists and news day.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-06-15  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 13:30 [gentoo-amd64] type1 xorg module missing Beso
2008-06-14 13:57 ` [gentoo-amd64] " Duncan
2008-06-14 15:07   ` Beso
2008-06-15  7:54     ` Duncan [this message]
2008-06-21 12:52       ` Duncan
2008-06-23  7:20         ` Beso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2008.06.15.07.54.06@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox