RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Dan Edward » Thu, 26 Oct 2000 04:00:00



Here's a problem that I have found.  If you install RH7 it comes with
gcc-2.96 which is a beta.  If you compile QT-2.2.1 under gcc-2.96 it appears
to work perfectly.  However if you try any QT examples it will error out.
After researching I found that this is know by troll and has commented on
hearing of issues compiling Qt under 2.96.  Well if you go ahead and compile
Kde 2.0 after compiling a broken QT because of gcc-2.96 you might and
usually will have issues.  The tricky thing is KDE will appear to compile
perfectly. The issue that I have seen on 6 of my systems I have tested this
on is they all hang after running startkde when it says "setting up
interprocess communication".  If anyone else wants to comment on this or has
found a solution or has had all the above packages and not had any problems
please post your experience with it and anything special you might have
done.

Dan

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Greg Reynold » Thu, 26 Oct 2000 04:00:00


Hi,
I had this problem and the answer is to compile qt with the brand new
glibc rpm from redhat.

    Cheers,

    Greg.

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Coy Kril » Thu, 26 Oct 2000 04:00:00


Brand new?  Can you give us the version/build information?  I'm only
finding one from Oct 5th.

Thanks,
Coy


> Hi,
> I had this problem and the answer is to compile qt with the brand new
> glibc rpm from redhat.

>     Cheers,

>     Greg.

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Kenan Esa » Fri, 27 Oct 2000 15:45:45


Quote:> Hi, I had this problem and the answer is to compile qt with the brand
> new glibc rpm from redhat.

You don't have to compile qt -- you can get a qt-2.1.1-rpm from Redhats
rawhide site. The KDE packages work with this one.

But I don't understand why the KDE-guys don't put THIS package to theirs.
KDE2.0 won't work on RH7.0 whithout the new qt-2.1.1-rpm.

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Greg Reynold » Fri, 27 Oct 2000 04:00:00


It's version glibc-2.1.94-3 that I got from the Redhat 7 update program
(but is available on the web too).

    Cheers,

    Greg.

PS It's a good idea to get this anyway.

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by ne.. » Sat, 28 Oct 2000 03:11:18



Quote:>> Hi, I had this problem and the answer is to compile qt with the brand
>> new glibc rpm from redhat.
>You don't have to compile qt -- you can get a qt-2.1.1-rpm from Redhats
>rawhide site. The KDE packages work with this one.

Aktually, the rpm you mention won't work. It is too
olde, if it was ever released. You need the latest qt
which is version 2.2.
[..]

--
Registered Linux User # 125653 (http://counter.li.org)
Moderation in all things.
                -- Publius Terentius Afer [Terence]
  2:10pm  up 4 days, 21:01, 10 users,  load average: 0.13, 0.06, 0.02

 
 
 

RH7, QT-2.2.1, and GCC-2.96 = 1 broken KDE 2.0

Post by Marvin R. Pierc » Sun, 29 Oct 2000 12:32:27



> It's version glibc-2.1.94-3 that I got from the Redhat 7 update program
> (but is available on the web too).

>     Cheers,

>     Greg.

> PS It's a good idea to get this anyway.

I installed using qt from KDE2-rc release without any problems whatsover.
It did however require that the libmng files were installed but the version
of the program is qt-2.2.1-3*. I did not install qt-profile.

My system is RH7 and has the new glibc-2.1.94-3 from RH. You can also get
qt-2.2.1-1 from Tucows.
Marvin

 
 
 

1. gcc-2.96/RH7,3 .vs gcc-3.2/RH8.0 portability issues

I have a fairly large application that was developed and built under gcc
2.96 (RH7.x). I have recently upgraded a Linux workstation to RH 8.0,
which installed gcc 3.2. The app no longer compiles.

the biggest problem had to do with STL header file issues (names,
location of templates, etc...). Poking around /usr/include/c++/3.2, I
noticed a 'backwards' directory.

Simply adding a "-I /usr/include/c++/3.2/backwards" seemed to take care
of STL issues.

However, I also have other header file problems (that were lost in the
volumes of STL errors/warnings I had previously got). For example,
'struct timeval' no longer was getting defined (even tho time.h and
bit/time.h were getting included).

Rather than try to deal with individual issues of this type as they
appeared, it seems like there must be a more reasonable approach that I
am unaware of...for example some king of "compatibility" switch on the
compile-line. I looked thru gcc documentation but nothing jumped out at me.

So my question is this:

Is there a "canonical" way to deal with this issue; in particular, a
compile-time compatibility flag that will permit gcc 2.96 apps to build
w/o having to modify source code?

Tx

- rich coco

2. IP Masquerading problem?

3. Slakware 96 kernel 2.0 to kernel 2.1

4. BeBox install information

5. filesystem not releasing space

6. build-in png support in qt-2.2.1 broken ?

7. tar and byte swap

8. KDE 2.1 with qt-2.3.0 from Rawhide 1.0

9. gcc-2.96 to gcc-2.95

10. RH7 & KDE 2.1 upgrade, No icons in kde menu

11. KDE 2.1, qt 2.3.0 - TrueType font rendering

12. AA woes: XFree86 4.0.3, QT 2.3.0 and KDE 2.1