Mail Archives: pgcc/1999/08/01/19:03:08
On Mon, 26 Jul 1999, Marc Lehmann wrote:
>On Fri, Jul 23, 1999 at 11:54:33AM -0500, Adam Norton wrote:
>> What are the issues about compliling Linux kernals Xservers etc. with PGCC.
>> Will it go out of the box? Or will I get to make changes?
>
>* Newer kernels (2.3.x, but NOT 2.2.x!) already have the necessary fixes to be
> compiled (I have not tried it, though). USe this line in the top Makefile:
>
> CFLAGS += $(shell if $(CC) -fno-strict-aliasing -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-fno-strict-aliasing"; fi)
>
>* X seems not yet to be ready for the next gcc and pgcc versions. My X is
> fully compiled with pgcc, yet the font libraries are known to break.
>
>* glibc also needs fixes for the next gcc and pgcc version, I recommened to
> use the following cflags until this is done:
> -D__NO_MATH_INLINES -D__NO_STRING_INLINES
>
>All of this is valid for current or soon-to-be-current gcc, egcs and pgcc
>versions, not specific to pgcc, which might have additional problems.
I tried compiling KDE (kdelibs), using gcc-2.95 but the build failed with
:
/bin/sh ../libtool --silent --mode=link g++ -O2 -Wall -s -o libkdecore.la
-rpath /opt/kde/lib -version-info 2:0 kconfig.lo kconfigbase.lo
ksimpleconfig.lo kcolorgroup.lo kapp.lo kurl.lo ksock.lo drag.lo
kprocess.lo kprocctrl.lo klocale.lo
libintl.lo fakes.lo kiconloader.lo kdebug.lo kstdaccel.lo kwm.lo
krootprop.lo kcharsets.lo kcharsetsdata.lo kchartables.lo kstring.lo
kpixmap.lo dither.lo kckey.lo kaccel.lo kglobalaccel.lo kclipboard.lo
krect.lo ksize.lo kpoint.lo
kconfigbase.lo: In function `qRound(double)':
kconfigbase.lo(.text+0x0): multiple definition of `qRound(double)'
kconfig.lo(.text+0x0): first defined here
kconfigbase.lo: In function `qRed(unsigned int)':
kconfigbase.lo(.text+0x58): multiple definition of `qRed(unsigned int)'
kconfig.lo(.text+0x58): first defined here
kconfigbase.lo: In function `qGreen(unsigned int)':
I could compile the same source using pgcc 1.1.3 (with -V option)
without any problems.
Is there any workaround for this failure, or do I have to wait for the
developpers of KDE to change the sources consequently ?
I had a problem applying the pgcc-2.95 patch : there were several failures
(mostly in texinfo dir), one of which was with gcc-2.95/gcc/java/parse.c.
Can I simply delete this file ?
j.
- Raw text -