User forums > General (but related to Code::Blocks)
Open Cascade 7.0.0 setup for Code::Blocks
StarBootics:
Hello everyone,
I need some help again about something I don't understand. I'm still trying to compile successfully OpenCascade but so far it fail saying :
--- Quote ---(0 error, 372 warning) built fail with error 7
--- End quote ---
This is what I don't understand you can't have "no error" and "an error" at the same time. So my question is : What kind of errors are being reported by Code::Blocks ?
I guess, syntax errors only
And if, by chance, someone know what error 7 from GCC compiler mean, this will be very helpful.
Thanks beforehand
StarBootics
BlueHazzard:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F
StarBootics:
I am running Code::Blocks version 16.01 rev 10692 on Ubuntu Gnome x64 (version 16.10).
The compiler I use is GNU GCC version (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005.
When I try to compile OpenCascade library, the compilation fail with 0 error 362 warning Built failed with error 7.
Build log : (Sorry too large to post it directly but for those who want to see it https://www.dropbox.com/s/sej40qsxlr2f4nq/Occt_Kernel_Build_log.zip?dl=0
--- Code: ---bin/Release/libOcctKernel.so -s) failed with error 7!
Process terminated with status -1 (110 minute(s), 15 second(s))
0 error(s), 362 warning(s) (110 minute(s), 15 second(s))
--- End code ---
Crash report: No crash
I didn't make a lot of test since the compilation time is very very long. But I have already tried :
To compile with C++14 instead of C++11
To built the library by dropping some portions out of it (bad idea even if the *.so library is created : undefinied references ...)
but none of them worked.
BlueHazzard:
i think this error comes from
--- Code: ---execvp(/bin/sh, -c, g++ .............
--- End code ---
and means:
--- Quote ---#define E2BIG 7 /* Argument list too long */
--- End quote ---
so the problem seems to be that there are too many .o files to link into one library at the same time. This is not a problem of the compiler but of the ?OS? or the way how codeblocks calls the compiler... This is a problem of the project file, not specially a hard bug in c::b, but c::b should be a able to handle this correctly...
someone an idea how to fix this?
StarBootics:
Perhaps compiling the library with CMake directly ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version