From: Juan Casero <juan@bellsouth.net>
To: "H.J. Lu" <hjl@lucon.org>
Cc: casero@beowulf.cox.miami.edu, 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: <Pine.LNX.3.96.980502211554.31823A-100000@elm> (raw)
In-Reply-To: <m0yVn5I-000268C@ocean.lucon.org>
Hi H.J. -
Thank you for your offer to help. After I installed libstdc++-2.8.0
everything worked out. I was a little confused at first because the egcs
developers mention that the standard c++ libraries come with the compiler
but apparently those who created the RPM binaries I used to install egcs
on my system did not include the libraries by default so I had to fetch
them from the same place and install them. So far I have successfully
compiled kdebase, kdelibs, kdesupport, kdegames, kdegraphics, and am
currently working on kdenetwork and the rest of the packages.
I had no choice but to use egcs. I have recently purchased SWiM motif 2.1
binaries compiled with the stock compiler that comes as part of RedHat
5.0. All of the code I compiled which used motif was not behaving
correctly. There were lots of problems with seg faults and file
filtering...etc. For two months I badgered the motif support personnel at
LSL regarding the problems. They finally figured out that the
c++ compiler in gcc-2.7.2.1 that comes stock with redhat 5.0 was not
generating the correct code. They sent me via email new binaries compiled
with egcs-1.02. I installed this compiler on my system and suddenly
the programs I have that make use of the motif shared libs are working
great. I recompiled my kernel with egcs and recompiled WindowMaker 0.14.1
also but I noticed that WindowMaker became exceedingly sluggish. It
worked but performance was very poor. I decided to move to fvwm 2.0.46
that came with RedHat 5.0 until I could find another solution. I hope I
will not have similar problems with KDE but I have to wait and see. If
KDE works well with my box such as it is then I will forego WindowMaker
altogether. GNUStep is nice but right now it is developing slowly. KDE
seems to be progressing much faster so I guess I'll just move over to it.
Would you consider making the egcs-1.03 release available as a binary RPM?
For some reason I still have gotten around to figuring out how to create
SPEC files and source RPMs on my redhat box. Compiling a source RPM is a
piece of cake if you have a working compiler.
Thanks..........
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, H.J. Lu wrote:
> >
> > 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
1998-05-02 18:56 ` Juan Casero [this message]
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.LNX.3.96.980502211554.31823A-100000@elm \
--to=juan@bellsouth.net \
--cc=casero@beowulf.cox.miami.edu \
--cc=dfox@belvdere.vip.best.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--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).