Error when compiling Codeblocks under Slackware 10.2

[kelo81]

Hello!!, I already posted this in another topic, but I think it was not the correct place to post it, so I'm creating a new topic with my problem (thanks for your patience  :shock:  )

Description:

I'm trying to follow the WIKI instructions to compile the source code from svn. I'm using slackware 10.2 without modify anything, and I can successfully install the wxGTK packages. But whe I try to run the ./bootstrap command, I get the message: Permission denied.
I'm using a root account!, so, what could be wrong here?, may anyone help me please?   

Thanks in advance!!!

[mandrav]

Try running chmod +x bootstrap first.

[kelo81]

Thank you!!!
Now the ./bootstrap command is working OK and I can start the compilation with make,
But.....

After a few minutes of compiling, I get this error:

In file included from codecompletion.cpp:43:
../../../src/sdk/editorcolourset.h:43: error: `wxSCI_KEYWORDSET_MAX' was not
   declared in this scope
../../../src/sdk/editorcolourset.h:51: error: `wxSCI_KEYWORDSET_MAX' was not
   declared in this scope
make[4]: *** [codecompletion.lo] Error 1
make[4]: Leaving directory `/root/Codeblocks/src/plugins/codecompletion'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/root/Codeblocks/src/plugins/codecompletion'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/Codeblocks/src/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/C

So, what could be the problem here?
Thanks in advance for your help!!!! 

[kelo81]

One more thing, when I ran the ./bootstrap I saw some warnings of "underquote" (or something like that) regarding the wx macros. But just warnings, not errors.
And the strange thing is that the compiling process worked fine during a few minutes (I mean, the wx lib appears to be installed OK), but then I get that error 

If someone can help me, I'll be very happy!   

[mandrav]

Seems like a missing #include. Will fix it tonight.

[kelo81]

OK Thanks, it is solved.... but now I'm getting this new one:

classbrowserbuilderthread.cpp: In member function `void
   ClassBrowserBuilderThread::AddChildrenOf(wxTreeCtrl*, wxTreeItemId, int,
   int)':
classbrowserbuilderthread.cpp:177: error: `DBGLOG' undeclared (first use this
   function)
classbrowserbuilderthread.cpp:177: error: (Each undeclared identifier is
   reported only once for each function it appears in.)
make[4]: *** [classbrowserbuilderthread.lo] Error 1
make[4]: Leaving directory `/root/Codeblocks/src/plugins/codecompletion'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/root/Codeblocks/src/plugins/codecompletion'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/Codeblocks/src/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Codeblocks/src'
make: *** [all-recursive] Error 1

[killerbot]

add
#include "messagemanager.h"

[mandrav]

Actually, comment it out. It shouldn't be there.

[kelo81]

I just added #include "messagemanager.h" and then it worked fine!! 
But.. why do you said that I have to comment it out?, I mean, just after including that header I was able to continue compiling... :shock:

I'm now trying the Linux distro under my Slackware 10.2 . Thank you very very much guys!!!!!!!!

[Game_Ender]

Just a security note, you should probably do as little as root as possible.  The only step of the Code::Blocks install that sould require system wide persmissions is "make install".

[mandrav]

But.. why do you said that I have to comment it out?, I mean, just after including that header I was able to continue compiling... :shock:

Because that was a debugging message which should be commented. And that class is a thread so it's possible to expect some unexpected crashes...

[kelo81]

OK, I understand... but if I coment it again, I'll get the error again, right?...
However, I'm now testing Codeblocks in Slackware, and It is working really good!!, You are the best developer team I never see!!!

Thanks for your amazing work!! 

[mandrav]

OK, I understand... but if I coment it again, I'll get the error again, right?...

No, it's already fixed in SVN.

[kelo81]

Ok thank you!!, I'll download it tonight  (I can't wait!)