News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

make fails if --enable-debug is used

Started by oBFusCATed, July 02, 2013, 12:32:59 AM

Previous topic - Next topic

oBFusCATed

Here is the failure:

de -I../../src/sdk/wxscintilla/include -I../../src/sdk/wxpropgrid/include -I../../src/include/tinyxml -I../../src/include/scripting/include -I../../src/include/scripting/bindings -I../../src/include/scripting/sqplus -I../../src/include/mozilla_chardet -I../../src/include/mozilla_chardet/mfbt -I../../src/include/mozilla_chardet/nsprpub/pr/include -I../../src/include/mozilla_chardet/xpcom -I../../src/include/mozilla_chardet/xpcom/base -I../../src/include/mozilla_chardet/xpcom/glue -ansi -DTIXML_USE_STL -g -DDEBUG -DCB_AUTOCONF -march=core2 -O2 -fweb -frename-registers -pipe -fPIC -DPIC -fexceptions -c mozilla_chardet/src/nsBig5Prober.cpp  -fPIC -DPIC -o .libs/nsBig5Prober.o
In file included from mozilla_chardet/src/nsBig5Prober.cpp:7:0:
../../src/include/mozilla_chardet/xpcom/glue/nsDebug.h:22:19: fatal error: prprf.h: No such file or directory
compilation terminated.
make[3]: *** [nsBig5Prober.lo] Error 1
make[3]: *** Waiting for unfinished jobs....


Should I commit a fix like this:

diff --git a/src/include/mozilla_chardet/xpcom/glue/nsDebug.h b/src/include/mozilla_chardet/xpcom/glue/nsDebug.h
index 0b2c1cf..1c60285 100644
--- a/src/include/mozilla_chardet/xpcom/glue/nsDebug.h
+++ b/src/include/mozilla_chardet/xpcom/glue/nsDebug.h
@@ -18,11 +18,11 @@
#include "mozilla/Assertions.h"
#include "mozilla/Likely.h"

-#ifdef DEBUG
+#ifdef BLABLA_DEBUG
#include "prprf.h"
#endif

-#ifdef DEBUG
+#ifdef BLABLA_DEBUG

/**
  * Abort the execution of the program if the expression evaluates to
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

MortenMacFly

Quote from: oBFusCATed on July 02, 2013, 12:32:59 AM
Should I commit a fix like this:

...

I would first check the Mozilla code base if they did fix it in a certain way and (if so) sync the sources with their repo.

If there are no updates, commit, but please embed changes of 3rd party libs into C::B comments so we can keep track of them.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

oBFusCATed

Quote from: MortenMacFly on July 16, 2013, 11:04:13 AM
I would first check the Mozilla code base if they did fix it in a certain way and (if so) sync the sources with their repo.
I doubt they've "fixed" it, because I think we have missing files, probably something that is deep in the include chains.
I'll wrap the changes in C::B tags, this was just a demonstration patch.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

MortenMacFly

Quote from: oBFusCATed on July 16, 2013, 11:34:34 AM
I'll wrap the changes in C::B tags, this was just a demonstration patch.
Wait a sec... for MOzilla we have a different approach I guess: the original files are copied to "filename.ext.old" and committed for reference here. (I think I did it did to the massive changes we did in several files.) So if there is already and ".old" file, you can ignore the wrapping comments. :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]