Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

rev 5993/5994 breaks build ? (solved : gch files are hell)

(1/3) > >>

killerbot:
I have already stared at this, and did some make clean's, or even starting from a bootstrap.
But on linux I already have 3 machines failing to build CB.
They all give this error :

--- Code: --- g++ -DHAVE_CONFIG_H -I. -I../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -I../../../src/include -I../../../src/include/wxscintilla/include -Ulinux -Uunix -O2 -ffast-math -DCB_AUTOCONF -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT codecompletion.lo -MD -MP -MF .deps/codecompletion.Tpo -c codecompletion.cpp  -fPIC -DPIC -o .libs/codecompletion.o
codecompletion.cpp: In member function ‘void CodeCompletion::OnOpenIncludeFile(wxCommandEvent&)’:
codecompletion.cpp:1920: error: ‘IsSuffixOfPath’ was not declared in this scope
make[4]: *** [codecompletion.lo] Error 1
make[4]: Leaving directory `/home/lieven/Projects/Codeblocks/trunk/src/plugins/codecompletion'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/lieven/Projects/Codeblocks/trunk/src/plugins/codecompletion'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/lieven/Projects/Codeblocks/trunk/src/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/lieven/Projects/Codeblocks/trunk/src'
make: *** [all-recursive] Error 1

--- End code ---

Anyone else suffering from this issue ?

Jenna:
We are at 6015 in the meantime, and this builds fine from project-file and with automake on my debian-machine and vista.

killerbot:
I am also at 6015, but the 'breaking' code was added in those revisions.
Now manually deleted all .gch files (since my experience always tend to end up with precompiled headers being utterly shit, yes I still love them ;-) ).
Anxious to see the result of that experiment ...

MortenMacFly:

--- Quote from: killerbot on January 01, 2010, 12:52:13 pm ---I am also at 6015, but the 'breaking' code was added in those revisions.

--- End quote ---
I am happy to assist. I've still some patches pending for CC. Hence this may be the reason for the broken build as my version of CC is heavily different. I tried to be as careful as possible when doing the "patch wave" (as you got aware obviously... ;-)), but maybe I missed some lines of code for the CC plugin.

Jenna:

--- Quote from: MortenMacFly on January 01, 2010, 01:07:17 pm ---
--- Quote from: killerbot on January 01, 2010, 12:52:13 pm ---I am also at 6015, but the 'breaking' code was added in those revisions.

--- End quote ---
I am happy to assist. I've still some patches pending for CC. Hence this may be the reason for the broken build as my version of CC is heavily different. I tried to be as careful as possible when doing the "patch wave" (as you got aware obviously... ;-)), but maybe I missed some lines of code for the CC plugin.

--- End quote ---
I don't think so, because it works here.

Navigation

[0] Message Index

[#] Next page