From: casero@beowulf.cox.miami.edu
To: "David E. Fox" <dfox@belvdere.vip.best.com>
Cc: kde-user@fiwi02.wiwi.uni-tuebingen.de, egcs@cygnus.com
Subject: Re: KDE and egcs
Date: Sat, 02 May 1998 10:47:00 -0000 [thread overview]
Message-ID: <Pine.A32.3.96.980502123222.13802A-100000@beowulf.cox.miami.edu> (raw)
In-Reply-To: <98050208034900.06447@belvdere>
I have already done that. I have kdesupport and kdelibs installed on my
box when I try to compile kdebase. I have compiled the Qt libs from
scratch using egcs-1.02 and installed them. I don''t know exactly where
the problem is. egcs-1.02 is supposed to come with its own copy of
libstdc++ but it is not immediately obvious where those libraries are. So
am in a rather complex predicament that I don't know how to solve. I need
egcs cuz the standard c++ compiler that comes with redhat 5.0 is buggy.
However, when I installed egcs now suddenly my old window manager breaks
and does not want to work properly even with a recompile. So I am forced
toresort to something like fvwm2 which seems to work well but is not very
aesthetically pleasing. In an effort to create a functional and
attractive desktop I decided to install KDE but now I learn that some
packages in KDE wont compile while others do. So right now I am stuck in
th hole. In fact this whole affair has become so frustrating that I have
considered installing Solaris 2.6 x86 on my box and removing Linux
altogether. The ultimtate end of a computer should be to make my work
easier and not to create more work for me.
Juan Casero
email: casero@beowulf.cox.miami.edu
__ _
/ / (_)__ __ ____ __
/ /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a
/____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . .
On Sat, 2 May 1998, David E. Fox wrote:
> On Fri, 01 May 1998, wrote:
> >Hi -
> >
> >I am having great difficulty compiling the kde base libs. Here is the
> >error
>
> You should try compiling kdesupport and installing it before you compile
> kdebase.
>
> >Juan Casero
> >email: casero@beowulf.cox.miami.edu
> > __ _
> > / / (_)__ __ ____ __
> > / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a
> >/____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . .
>
> --
> ------------------------------------------------------------------------
> David E. Fox Tax Thanks for letting me
> dfox@belvdere.vip.best.com the change magnetic patterns
> root@belvedere.sbay.org churches on your hard disk.
> -----------------------------------------------------------------------
>
>
next parent reply other threads:[~1998-05-02 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98050208034900.06447@belvdere>
1998-05-02 10:47 ` casero [this message]
1998-05-02 18:56 ` H.J. Lu
1998-05-02 18:56 ` Juan Casero
1998-05-01 21:25 casero
-- strict thread matches above, loose matches on Subject: below --
1998-05-01 19:37 Juan Casero
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=Pine.A32.3.96.980502123222.13802A-100000@beowulf.cox.miami.edu \
--to=casero@beowulf.cox.miami.edu \
--cc=dfox@belvdere.vip.best.com \
--cc=egcs@cygnus.com \
--cc=kde-user@fiwi02.wiwi.uni-tuebingen.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).