From: hjl@lucon.org (H.J. Lu)
To: casero@beowulf.cox.miami.edu
Cc: dfox@belvdere.vip.best.com,
kde-user@fiwi02.wiwi.uni-tuebingen.de, egcs@cygnus.com
Subject: Re: KDE and egcs
Date: Sat, 02 May 1998 18:56:00 -0000 [thread overview]
Message-ID: <m0yVn5I-000268C@ocean.lucon.org> (raw)
In-Reply-To: <Pine.A32.3.96.980502123222.13802A-100000@beowulf.cox.miami.edu>
>
> 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
You did even mention how you configured/installed egcs on RedHat 5.0.
> egcs cuz the standard c++ compiler that comes with redhat 5.0 is buggy.
I have warned many months ago that the current default configuration
for egcs might cause problems for people on Linux who want to install
egcs as their default compiler. The default Linux configuration in
egcs 1.0.2 was not designed to be used as the default compiler. You
may run into the problem I have warned before.
> However, when I installed egcs now suddenly my old window manager breaks
You need to give more details on your problem.
> 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
I have no problem to compile fvwm2 on RH 5.0 with egcs 1.0.2.
> 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
I have make egcs 1.0.2 linux/x86 binaries avaialable. Please check
out
ftp://tsx-11.mit.edu/pub/linux/packages/GCC
Please do read my release note. If you want to install it, you should
remove ALL your previous egcs 1.0.2 from your system.
BTW, I will also make egcs 1.0.3 linux/x86 binaries when it is released
to public.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-05-02 18:56 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
1998-05-02 18:56 ` H.J. Lu [this message]
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=m0yVn5I-000268C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=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).