Dtd location??

I just had a problem building kdebase.  Acutally I was trying to rebuild it after the first successful time
but I got a similar problem trying to build kdeutils, I was trying to find the location for the dtd's and if I
could just simply copy them in a certain location so these builds would complete.

gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/pics'
Making all in favicons
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/favicons'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/favicons'
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq'
gmake[2]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq'
Making all in applnk
gmake[2]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk'
Making all in compat
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk/compat'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk/compat'
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk'
gmake[2]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/applnk'
Making all in doc
gmake[2]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/doc'
Making all in .
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/doc'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/doc'

RE: Dtd location??

I apologize , I rebounded and dunked my own miss by modifying the bzip2 Makfile from Redhat that creates a
shared library and compiling it...
all: $(OBJS)
        $(CC) -G -o libbz2.so.1.0 $(OBJS)
#       $(CC) $(CFLAGS) -o bzip2-shared bzip2.c libbz2.so.1.0.2
        rm -f libbz2.so.1.0
        ln -s libbz2.so.1.0.2 libbz2.so.1.0

The newer gcc that I built on solaris are now only using solaris ld in /usr/ccs/bin/ld (I wish I knew how to
change that) so the makefile had to be modified.

This seemed to produce a bzip2 shared library that kdelibs liked and is now attempting to build the
kdedoctools for the new installation instead of an old installation I had working for a few years.

Tony
-----Original Message-----
From: Johnson, Tony -Research [mailto:gjohnson <at> ADMWORLD.com] 
Sent: Tuesday, July 06, 2004 10:35 AM
To: kde-solaris <at> kde.org
Subject: [kde-solaris] Dtd location??

I just had a problem building kdebase.  Acutally I was trying to rebuild it after the first successful time
but I got a similar problem trying to build kdeutils, I was trying to find the location for the dtd's and if I
could just simply copy them in a certain location so these builds would complete.

gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/pics'
Making all in favicons
gmake[3]: Entering directory `/export/home/gjohnson/kde323/kdebase-3.2.3/libkonq/favicons'
gmake[3]: Nothing to be done for `all'.

kdelibs 3.2.2 compilation Problem

Hello every one,

I have some serious problem by compiling kdelibs with the C Compiler 
ditributed by SUN. I don't have any idea why the compiler show me this 
error. I just begin to be crazy. I visited all the Mailing list and I 
try to find something about this error on the web.

I'll be very happy, if someone have an idea.

/bin/bash ../libtool --silent --mode=link --tag=CXX CC 
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT 
-DQT_NO_TRANSLATION   -L/usr/local/jpeglib/6b/lib 
-R/usr/local/jpeglib/6b/lib -L/usr/ucblib -R/usr/ucblib 
-L/usr/local/bzip2/1.0.2/lib -R/usr/local/bzip2/1.0.2/lib 
-L/usr/local/kde/3.2.2/lib -R/usr/local/kde/3.2.2/lib 
-L/usr/local/qt/3.3.2/lib -R/usr/local/qt/3.3.2/lib -L/usr/lib 
-R/usr/lib  -o libkdecore.la -rpath /usr/local/kde/3.2.2/lib 
-L/usr/local/qt/3.3.2/lib -R /usr/local/kde/3.2.2/lib -R 
/usr/local/qt/3.3.2/lib -mt   -version-info 6:0:2 -no-undefined 
libintl.lo kapplication.lo kdebug.lo netwm.lo kconfigbase.lo kconfig.lo 
ksimpleconfig.lo kconfigbackend.lo kmanagerselection.lo kdesktopfile.lo 
kstandarddirs.lo ksock.lo kpty.lo kprocess.lo kprocctrl.lo klocale.lo 
krfcdate.lo kiconeffect.lo kicontheme.lo kiconloader.lo kwin.lo 
kwinmodule.lo krootprop.lo kcharsets.lo kckey.lo kshortcut.lo 
kkeynative_x11.lo kkeyserver_x11.lo kaccelaction.lo kshortcutmenu.lo 
kaccelbase.lo kaccel.lo kglobalaccel_x11.lo kglobalaccel.lo kstdaccel.lo 
kshortcutlist.lo kcrash.lo kurl.lo kregexp.lo kglobal.lo 
kglobalsettings.lo kallocator.lo kvmallocator.lo kmimesourcefactory.lo 
kinstance.lo kpalette.lo kipc.lo klibloader.lo ktempfile.lo 
kuniqueapplication.lo kaccelmanager.lo ksavefile.lo krandomsequence.lo 

Re: kdelibs 3.2.2 compilation Problem

It seems to me that it's missing -lqt-mt on the linker line (the QT3 
library). Could you please try to add it and see if it helps.

--Stefan

------ 

On Monday 12 July 2004 11:58, Héctor López Romero wrote:
> Hello every one,
>
> I have some serious problem by compiling kdelibs with the C
> Compiler ditributed by SUN. I don't have any idea why the compiler
> show me this error. I just begin to be crazy. I visited all the
> Mailing list and I try to find something about this error on the
> web.
>
> I'll be very happy, if someone have an idea.

[ ... snip snip ... ]

> Greetings Hector

--

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman <at> nyc.rr.com                          -Monty Python

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.

kdelibs 3.2.2 compilation Problem

Hi Stefan,

I use the lqt-mt and I got the same error as before.
I just install Qt correctly (configure with option -thread -xft 
-qt-libpng -qt-libjpeg -qt-libmng -qt-zlib -qt-gif -debug) and the 
library qstringlist.h exist!

Any idea?

Hector

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Re: kdelibs 3.2.2 compilation Problem

Hmmm.  This looks like a template instantiation problem then.

Could you add the following flags to CXX:

-verbose=template -instances=extern -template=extdef,geninlinefuncs

This will force the compiler to print to stdout the template 
generation phase verbose and it shows whether or not the 
QStringList::operator+= has actually been instantiated.

I would suggest that you rebuild this library from scratch with these 
new flags and save this output to a file (makes it easier to seach 
for operator+=).

--Stefan

-----

On Tuesday 13 July 2004 06:20, Héctor López Romero wrote:
> Hi Stefan,
>
> I use the lqt-mt and I got the same error as before.
> I just install Qt correctly (configure with option -thread -xft
> -qt-libpng -qt-libjpeg -qt-libmng -qt-zlib -qt-gif -debug) and the
> library qstringlist.h exist!
>
> Any idea?
>
> Hector

Re: kdelibs 3.2.2 compilation Problem

On Monday 12 July 2004 17:58, Héctor López Romero wrote:
> Hello every one,

Hi Hector,

maybe that it helps to delete the whole cache:

rm -rf
 /net/hermes/software/local/kde/sunos5.7-32/3.2.2/src/kdelibs-3.2.2/kdecore/.libs/SunWS_cache/

It's often a severe problem with this cache using the Sun Workshop compiler.

regards
rainald

> I have some serious problem by compiling kdelibs with the C Compiler
> ditributed by SUN. I don't have any idea why the compiler show me this
> error. I just begin to be crazy. I visited all the Mailing list and I
> try to find something about this error on the web.
>
> I'll be very happy, if someone have an idea.
>
>
>
> /bin/bash ../libtool --silent --mode=link --tag=CXX CC
> -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
> -DQT_NO_TRANSLATION   -L/usr/local/jpeglib/6b/lib
> -R/usr/local/jpeglib/6b/lib -L/usr/ucblib -R/usr/ucblib
> -L/usr/local/bzip2/1.0.2/lib -R/usr/local/bzip2/1.0.2/lib
> -L/usr/local/kde/3.2.2/lib -R/usr/local/kde/3.2.2/lib

Re: kde-solaris Digest, Vol 16, Issue 3

Hello Stefan,

> Could you add the following flags to CXX:
> 
> -verbose=template -instances=extern -template=extdef,geninlinefuncs
> 
> This will force the compiler to print to stdout the template 
> generation phase verbose and it shows whether or not the 
> QStringList::operator+= has actually been instantiated.
> 
> I would suggest that you rebuild this library from scratch with these 
> new flags and save this output to a file (makes it easier to seach 
> for operator+=).

I tried already this option, but the displayed info does n't help.
I decided to look on all the files on the sub-directory and search on 
the files that contain the character "QSTringList". After that I just 
tried to remplace the += command for <<, because  "<<" is already 
defined on the qt library <qstringlist.h>.

Even this experiment was n't successfully! I get the same error.

I try another variant purposed from Rainald. He purpose to delete 
completly the SunWS_cache/CC_obj_5 subdirectory and expect that the 
compiler generate it again. The result of this experiment was, that I 
get: "The library on SunWS_cache/CC_obj_5 not exist and the compiler 
does n't generate a new one.

I restore the subdirectory and I am on the same place like before.

Re: template instantiation problems

The last trick i would try is to declare the QStringList variable in 
question as volatile, hoping that the volatile qualifier will force 
the compiler to instantiate all needed member methods of the 
template. 

If this doesnt work either, then the only fix is to change the 
template instantiation method from "extern" to "global":

CXXFLAGS += " -features=%all,extensions -instances=global \ 
-template=geninlinefuncs -verbose=template"

This means that templates will now be instantiated within the object 
file, for each object, instead of using a separate template 
repository. This (global) is the method i use.

Make absolutely sure that, at link time,  you do _not_ call the linker 
directly, but you link with

$(CXX) $(CXXFLAGS) $(LDFLAGS)

The drawback of this method is that you have to rebuild absolutely 
everything from scratch, by doing a "make clean".

Deleting the SunWS_cache directory without doing a "make clean" is 
never a good idea. It always ends up in trouble.

KDE _can_ be built with SunProCC. 

--Stefan

kdeinit >= 3.2, Solaris >= 9, crash

Hi all

 I still have the problem that kdeinit 3.2 crashes when it should
start konqueror on Solaris9 or Solaris10 systems. This problem
is new in KDE 3.2. Kdeinit from 3.1.4 works well in Solaris9/10 as
does kdeinit3.2 in Solaris8. Konqueror itself has no problems
when it got startet manually form the command line.

 The problem is common to both platforms Solaris/SPARC and
Solaris/x86.

The command:
	dcopstart konqueror
terminamtes with:
	Error: KDEInit could not launch 'konqueror'
and leaves a core file.

gdb /usr/local/KDE/3.2.3/bin/kdeinit core
GNU gdb 6.1
	.
	.
Core was generated by `kdeinit +kcminit +knotify'.
Program terminated with signal 11, Segmentation fault.
	.
	.
(gdb) where
#0  0xcf350af2 in free_unlocked () from /usr/lib/libmalloc.so.1
#1  0xcf350a78 in free () from /usr/lib/libmalloc.so.1
#2  0xcf2cf59d in _XimCheckIfLocalProcessing ()