User forums > Help
Compilation error with SuSE Linux 9.3 on AMD64
mandrav:
Wait, I have a hunch:
Try deleting the new project wizard plugin...
Edit: yes, this should be the reason. I haven't built this plugin in my Ubuntu64 yet because I know it won't work. That explains everything now.
MortenMacFly:
mandrav, I really appreciate how you are trying to help... anyway:
--- Quote from: mandrav on May 03, 2006, 03:44:13 pm ---Try deleting the new project wizard plugin...
--- End quote ---
I've done that with and without the #ifdef in scriptbindings.cpp.
--- Quote from: mandrav on May 03, 2006, 03:44:13 pm ---Edit: yes, this should be the reason. [...]
--- End quote ---
The result: I come (indeed!) one step further having done that. I see the compiler selection dialog and then a message box pops up complaining that an unnused lock file in /tmp has been removed. I click ok and I'm back on the compiler select dialog. I select the GCC compiler and hit OK and (unfortunately) then I receive the same assertion.
To sum up: Yes, C::B runs further but still I believe since the AS engine object is constructed anyway which calls RegisterAnyObject it is not surprising that the assertion is raised. I would guess that it is issued later now because the asEngine object is not creeted in the project wizard plugin but somehwere else... :-(
I think to really get rid of this issue the construction of the AS engine should be ommited. But how to do that? And (more important): Does it make sense to find a workaround for this knowing that the real issue (AS 64 bit incompatibility) is already being investigated? Again: I really appreciate you are trying to help me but maybe we are "fighting" on the wrong place...?!
With best regards, Morten.
mandrav:
What doesn't make sense is for me (and anyone else I know with 64bit systems) AS doesn't get in the way: it just doesn't work. But the rest of the program does...
Anyway, I 'll try to fix this tonight.
takeshimiya:
--- Quote from: MortenMacFly on May 03, 2006, 02:33:23 pm ---That's because the software I'm developing is used primary on Windows and secondary on that server where I still have to use Makefiles for development which simply sucks. Anyway: Running any linux system remotely for testing which can run C::B is helpful, too. That would be the case with Ubuntu...
--- End quote ---
You can use C::B in your Windows pc and compile remotely in your Linux server: http://forums.codeblocks.org/index.php?topic=2378.0 :wink:
mandrav:
Morten,
I can't make it go wrong here.
Are you allowed to use the debugger in that linux server? It would help a lot if we could get our hands on the backtrace...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version