Originally created by: grtht... (code.google.com)@gmail.com
*What steps will reproduce the problem?*
1.cmake /workingpath/fg11-1018_w_CMAKE/flightgear
2. make -j5
3.
*What is the expected output? What do you see instead?*
fgfs built
*Any output in the console (black window)?*
92%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/flight_control/FGMagnetometer.cpp.o
Linking CXX static library libfgFDM.a
[ 93%] [ 93%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/flight_control/FGPID.cpp.o
Built target fgFDM
[ 93%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/flight_control/FGSensor.cpp.o
[ 93%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/flight_control/FGSummer.cpp.o
[ 93%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/flight_control/FGSwitch.cpp.o
[ 93%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGElectric.cpp.o
[ 94%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGEngine.cpp.o
[ 94%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGForce.cpp.o
[ 94%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGNozzle.cpp.o
[ 94%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGPiston.cpp.o
[ 94%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGPropeller.cpp.o
[ 95%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGRocket.cpp.o
[ 95%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGRotor.cpp.o
[ 95%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGTank.cpp.o
[ 95%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGThruster.cpp.o
[ 95%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGTurbine.cpp.o
[ 96%] Building CXX object src/FDM/JSBSim/CMakeFiles/fgJSBSim.dir/models/propulsion/FGTurboProp.cpp.o
Linking CXX static library libfgJSBSim.a
[ 96%] Built target fgJSBSim
make: *** [all] Erreur 2
*What FlightGear version are you using (when using GIT version, please
mention date)?*
git 2011-10-18
*What operating system and graphics card?*
opebsuse 11.4
*Please provide any additional information below or as attachment (Avoid
expiring external links, such as to imageshack/pastebin/...).*
Since cmake was there, we were curious about it .
Probably not in use and not operational.
Our approach Was just experimental, since we use to build with.
autogen, configure, make, which works perfectly.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: grtht... (code.google.com)@gmail.com
A second make behind override the first error, however , getting a bunch of others message errors on console.
ending with
[100%] Building CXX object src/Main/CMakeFiles/fgfs.dir/renderer.cxx.o
[100%] Building CXX object src/Main/CMakeFiles/fgfs.dir/splash.cxx.o
[100%] Building CXX object src/Main/CMakeFiles/fgfs.dir/util.cxx.o
[100%] Building CXX object src/Main/CMakeFiles/fgfs.dir/viewer.cxx.o
[100%] Building CXX object src/Main/CMakeFiles/fgfs.dir/viewmgr.cxx.o
Linking CXX executable fgfs
[100%] Built target fgfs
make: *** [all] Erreur 2
Do not get the fgfs executable.
Sorry, forget that message, the fg cmake build process is definitively broken.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: wonco...@googlemail.com
According to your last post, the compilation seems to succeed, it is the linker that fails apparently there?
Besides, the information you have posted is not very complete or useful, this is working for me on OpenSUSE 11.3, using completely fresh checkouts and a custom install prefix.
What linker are you using?
Have you tried a non-parallel build?
That _could_ be the cause, if the linker is getting invoked in parallel by several instances of make.
If that still fails, have you tried checking out FRESH copies of OpenAL/PLIB/OSG/SG/FG and installing them to a new custom prefix?
For example, use: --DCMAKE_INSTALL_PREFIX=~/cmake_test
This is the easiest way to ensure that you are building (and linking!) using the right dependencies, so that the build process doesn't mix libraries from other places.
Finally, note that IF your build process segfaults repeatedly (despite using NO optimizations and NO parallel builds) and if it can be directly resumed by restarting it, only to segfault at a later stage, that this may be related to hardware issues (such as faulty RAM/HD).
Also, probably worth adding to the README.cmake: if cmake doesn't configure "out-of-source", it is possible that there's still a CMakeCache.txt file in your source tree, this needs to be deleted first: http://www.cmake.org/Wiki/CMake_FAQ#I_run_an_out-of-source_build_but_CMake_generates_in-source_anyway._Why.3F
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: wonco...@googlemail.com
Note that if this is related to your use of parallel builds, you should be able to continue and complete the build by just running "make", without having to start from scratch.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: grtht... (code.google.com)@gmail.com
Oh yes that's right,
that FG cmake does not like multi core CPU, which looks to be a regression, since we invest in multi core cpu.
however fgadmin does not build/link, i had to remove it with ccmake fgadmin "off".
Well let's go on with autogen , configure, and make -jX which is the quickest, most performant. at least with FG.
Thanks
David
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cumuluni... (code.google.com)@gmail.com
Just for the record: make -j25 runs fine (and fast) here on a Linux box with cmake.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: wonco...@googlemail.com
I also didn't have any problems doing a parallel cmake build on a 16 core Linux box.
Regarding comment #5: Were you able to complete the build now, as a non-parallel build?
> Well let's go on with autogen , configure, and make -jX which is the quickest, most performant. at least with FG.
Even when using cmake, you'll still get Makefiles on Linux/Unix.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: grtht... (code.google.com)@gmail.com
>Regarding comment #5: Were you able to complete the build now, as a non-parallel build?
Yes, but the fgadmin issue , like said upper
So, without fgadmin and non-parallel build it does build
David
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: victhor.... (code.google.com)@gmail.com
Just for the record, I also was unable to build fg with cmake, also with parallel build(make -j5). I got a error while building fgpanel. After disabling fgpanel from build using "cmake CMakeLists.txt -DWITH_FGPANEL:BOOL=OFF", I was able to build fg with make -j5. FG works fine.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
There is no issue with parallel builds. "make" always stops immediately when any error occurs. So, if any utility/program fails to compile/link, then the entire parallel build stops immdiately - even when other build threads (and programs) could be built normally. That's normal GNU make behaviour. A parallel make only succeeds if all threads/builds succeed. So the only problem here is to solve the fgadmin/fgpanel linker issues.
Mergedinto: 480
Status: Duplicate