kdelibs from CVS (Nov 16) compile problem

kdelibs from CVS (Nov 16) compile problem

Post by Robert_ » Wed, 21 Nov 2001 05:15:41



Hi,
I tried this on the kde newgroup with no answer so thought I'd try a couple
of other newsgroups.
I'm trying to compile kde3 from CVS
(had never tried it so wanted to give it a go).  
I managed to finally get the kdelibs configure script happy,
and kdelibs compiled for about an hour when it stopped on the following:
kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
make[3]: *** [kjs_proxy.lo] Error 1

Has anyone seen this or know what the solution is?

This file exists in the tree in:
/khtml/ecma/kprotocolmanager.h
and is called from /khtml/ecma/kjs_proxy.cpp as:
#include <kprotocolmanager.h>

In case its relevent here is a longer snippet from the compile errors:
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../khtml
-I../../khtml/misc -I../../khtml/css -I../../khtml/dom -I../../khtml/xml
-I../../khtml/html -I../../dcop -I../../libltdl -I../../kdecore
-I../../kdeui -I../../kssl -I/usr/local/qt/include -I.
-I/usr/local/kde/include -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/local/include -O2 -fno-exceptions -fno-check-new -ftemplate-depth-99
-DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT
-fexceptions -UQT_NO_COMPAT -Wp,-MD,.deps/kjs_proxy.pp -c kjs_proxy.cpp  
-fPIC -DPIC -o .libs/kjs_proxy.o
kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
make[3]: *** [kjs_proxy.lo] Error 1
make[3]: Leaving directory `/usr/local/kde/kdelibs/khtml/ecma'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/kde/kdelibs/khtml'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/kde/kdelibs'
make: *** [all-recursive-am] Error 2

(Compiling on Slackware 8.0)

all the best,
Robert_L
--
Linux Mandrake release 8.0 (Traktopel) for i586
Kernel 2.4.13   XFree86 4.1.0  
KDE: 2.2.1    KNode: 0.6.1

 
 
 

kdelibs from CVS (Nov 16) compile problem

Post by Richar » Wed, 21 Nov 2001 14:27:15


In C or C++ #include <example.h> means that the compiler expects
example.h to exist in the "include path" of the compiler. whereas
#include "example.h" is expected to exist in the same directory as the
file being compiled. So try editing kjs_proxy.cpp and change the line
#include <kprotocolmanager.h> to
#include "kprotocolmanager.h"

Richard :)


> Hi,
> I tried this on the kde newgroup with no answer so thought I'd try a couple
> of other newsgroups.
> I'm trying to compile kde3 from CVS
> (had never tried it so wanted to give it a go).  
> I managed to finally get the kdelibs configure script happy,
> and kdelibs compiled for about an hour when it stopped on the following:
> kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
> make[3]: *** [kjs_proxy.lo] Error 1

> Has anyone seen this or know what the solution is?

> This file exists in the tree in:
> /khtml/ecma/kprotocolmanager.h
> and is called from /khtml/ecma/kjs_proxy.cpp as:
> #include <kprotocolmanager.h>

> In case its relevent here is a longer snippet from the compile errors:
> g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../khtml
> -I../../khtml/misc -I../../khtml/css -I../../khtml/dom -I../../khtml/xml
> -I../../khtml/html -I../../dcop -I../../libltdl -I../../kdecore
> -I../../kdeui -I../../kssl -I/usr/local/qt/include -I.
> -I/usr/local/kde/include -DQT_THREAD_SUPPORT -D_REENTRANT
> -I/usr/local/include -O2 -fno-exceptions -fno-check-new -ftemplate-depth-99
> -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT
> -fexceptions -UQT_NO_COMPAT -Wp,-MD,.deps/kjs_proxy.pp -c kjs_proxy.cpp  
> -fPIC -DPIC -o .libs/kjs_proxy.o
> kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
> make[3]: *** [kjs_proxy.lo] Error 1
> make[3]: Leaving directory `/usr/local/kde/kdelibs/khtml/ecma'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/usr/local/kde/kdelibs/khtml'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/local/kde/kdelibs'
> make: *** [all-recursive-am] Error 2

> (Compiling on Slackware 8.0)

> all the best,
> Robert_L


 
 
 

kdelibs from CVS (Nov 16) compile problem

Post by Robert_ » Wed, 21 Nov 2001 10:47:40



> In C or C++ #include <example.h> means that the compiler expects
> example.h to exist in the "include path" of the compiler. whereas
> #include "example.h" is expected to exist in the same directory as the
> file being compiled. So try editing kjs_proxy.cpp and change the line
> #include <kprotocolmanager.h> to
> #include "kprotocolmanager.h"

> Richard :)


<snip>
>> I managed to finally get the kdelibs configure script happy,
>> and kdelibs compiled for about an hour when it stopped on the following:
>> kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
>> make[3]: *** [kjs_proxy.lo] Error 1

>> Has anyone seen this or know what the solution is?

<snip>
Thanks for the info- I'll give that a shot.
Unfortunately this error happens an hour into the compile so I won't know
for a while ;-(   No doubt there are ways to step through it without
starting over every time you try a fix.
again, thanks for taking the time
Robert_L

--
Linux Mandrake release 8.0 (Traktopel) for i586
Kernel 2.4.13   XFree86 4.1.0  
KDE: 2.2.1    KNode: 0.6.1

 
 
 

kdelibs from CVS (Nov 16) compile problem

Post by Robert_ » Wed, 21 Nov 2001 20:02:08




>> In C or C++ #include <example.h> means that the compiler expects
>> example.h to exist in the "include path" of the compiler. whereas
>> #include "example.h" is expected to exist in the same directory as the
>> file being compiled. So try editing kjs_proxy.cpp and change the line
>> #include <kprotocolmanager.h> to
>> #include "kprotocolmanager.h"

>> Richard :)


> <snip>
>>> I managed to finally get the kdelibs configure script happy,
>>> and kdelibs compiled for about an hour when it stopped on the following:
>>> kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
>>> make[3]: *** [kjs_proxy.lo] Error 1

>>> Has anyone seen this or know what the solution is?
> <snip>
> Thanks for the info- I'll give that a shot.

Smooth sailing after implementing your suggestion.  I've moved on to
kdebase and its compiling now.
:-)
Thanks,
Robert_L
 
 
 

1. kdelib from CVS (Nov 16) compile problem

Hi,
I'm trying to compile kde3 from cvs
(had never tried it so wanted to give it a go).  
I managed to finally get the kdelibs configure script happy,
and kdelibs compiled for about an hour when it stopped on the following:
kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
make[3]: *** [kjs_proxy.lo] Error 1
Has anyone seen this or know what the solution is?
This file exists in the tree in:
/khtml/ecma/kprotocolmanager.h
and is called from /khtml/ecma/kjs_proxy.cpp as:
#include <kprotocolmanager.h>
In case its relevent here is a longer snippet from the compile errors:
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../khtml
-I../../khtml/misc -I../../khtml/css -I../../khtml/dom -I../../khtml/xml
-I../../khtml/html -I../../dcop -I../../libltdl -I../../kdecore
-I../../kdeui -I../../kssl -I/usr/local/qt/include -I.
-I/usr/local/kde/include -DQT_THREAD_SUPPORT -D_REENTRANT
-I/usr/local/include -O2 -fno-exceptions -fno-check-new -ftemplate-depth-99
-DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT
-fexceptions -UQT_NO_COMPAT -Wp,-MD,.deps/kjs_proxy.pp -c kjs_proxy.cpp  
-fPIC -DPIC -o .libs/kjs_proxy.o
kjs_proxy.cpp:27: kprotocolmanager.h: No such file or directory
make[3]: *** [kjs_proxy.lo] Error 1
make[3]: Leaving directory `/usr/local/kde/kdelibs/khtml/ecma'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/kde/kdelibs/khtml'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/kde/kdelibs'
make: *** [all-recursive-am] Error 2
(Compiling on Slackware 8.0)

all the best,
Robert_L

2. Modem -- lights flash but no-ones in...

3. Compile kdelibs [CVS] on Solaris 7

4. Watch program available ? ? ?

5. error trying to compile KDELIBs 2.2 from the sources in the KDE CVS server.

6. ZIP Drive Problem

7. KDE 3.0beta2 CVS on 3/17/01 - KDELIBS wont compile?

8. What the hell does GNU STAND FOR?????????????????????????????????

9. CVS kdelibs comilation problem.

10. Problem With KDELIBS make -f Makefile.cvs

11. CLUB: Linux User Group of Davis - Nov. 16 - C Programming

12. COLA FAQ 5 of 7 16-Nov-2002

13. COLA FAQ 4 of 7 16-Nov-2002