From: "James B. Parker" <pajama1@mindspring.com>
To: LinuxPPC Developer <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Xfree86 4.0
Date: Mon, 13 Mar 2000 14:56:34 -0500 [thread overview]
Message-ID: <B4F2B222.152C%pajama1@mindspring.com> (raw)
In-Reply-To: <38CD39B5.A91B1B92@erols.com>
<snip> from pogtal@erols.com on 3/13/00 1:55 PM
> "James B. Parker" wrote:
>
>> _first_
>> It asks for a file call libqt.0.2 or something like that (I know the libqt
>> part is correct). Although this problem may have cleared up after I built
>> it a second time, I tried to reinstall KDE from a rpm (thinking this may
>> solve the second issue) and a message was displayed requesting the above
>> mentioned file.
>
> I would assume that libqt (probably libqt.so.2 or something like that) is part
> of the qt developement package..
>
> According to rpmfind.net, libqt.so.2 is provided by the qt package, you
> probably also want the qt-devel package.
I was a little incorrect. It is looking for liqt.so.1 and I have libqt.so.2
in my libs folder. But I will install the qt dev package and see what
happens.
>
>> _second_
>> When I try to start the server (xinit, startx, X) there is a fatal error:
>> no screens
>
> What is the fatal error? I don't think this would be related to the libqt, as
> qt is a kde package for graphics, and shouldn't be related to the X server
> working/not working (AFAIK).
>
> What is the fatal error?
>> no screens
no screens
James
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-13 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 18:39 Xfree86 4.0 James B. Parker
2000-03-13 18:55 ` Nelson Abramson
2000-03-13 19:56 ` James B. Parker [this message]
2000-03-13 18:59 ` Michael Schmitz
2000-03-13 19:59 ` James B. Parker
2000-03-13 22:07 ` phandel
2000-03-14 9:51 ` Michael Schmitz
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=B4F2B222.152C%pajama1@mindspring.com \
--to=pajama1@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.