If there is something that we could fix that prevents previous versions
of flightgear or an ancillary package such as fgrun from building
correctly, should we fix it in the git branches for our releases?
At this point neither Flightgear or fgrun versions 2.10.1, 2.10.0 or
2.8.0 build for me on Ubuntu 13.04. Changes to 2 CmakeLists.txt
files are already made and work on 13.04 in 2.12.0.
If I ask for a merge of the two corrected CMakeLists.txt files in
Flightgear and FGRUN 2.10.1, 2.10.0 and 2.8.0, how will this be
received. Would these patches be accepted and merged to the 2.10.0 and
2.8.0 branches? Would the tag for 2.10.0 and 2.8.0 be updated?
I won't do any work on this unless its agreed in advance that the
patches should be merged and what tags should or should not be updated.
Does anyone care about 2.10 at this point?
What are your thoughts on updates to previous versions to keep them
viable?
-Pat
Background.
In recent months, after upgrading to Ubuntu
13.04, I was seeing errors like the one below when building flightgear
or fgrun on the 13.04 installation. Building on Ubuntu 12.10 continues
to work correctly. The problem is fixed in Flightgear branches next
master and 2.12.0
There are two small patches to CMakeLists.txt that address this. one for
flightgear, the other for fgrun. While next, master and 2.12.0 have
them, earlier branches do not. Without these patches, flightgear and
fgrun will not compile on Ubuntu 13.04.
Causes:
There are reports from several open source projects attempting to build
against fltk on various distributions, having the exact same issue.
From what I've read, the problem may lie in one of several possible
areas:
o changes in the way libraries are structured by distributions.
These changes seem to require libdl to be explicitly included at some
level in applications that use fltk such as Flightgear. Previous
version of the distribution did not have this issue.
o Static linking vs dynamic linking
There's a note regarding this on the FLTK mailing lists
o Cmake's find_FLTK
Shouldn't this include libdl when necessary?
Has this been done for any version of fltk?
Has this been done in any version of CMake.
I'll inquire on the fltk mailing list.
-Pat
[ 99%] Built target FGAdminUI
Linking CXX executable fgadmin
/usr/bin/ld: /usr/lib/i386-linux-gnu/libfltk.a(Fl_Preferences.o):
undefined reference to symbol 'dlopen@@GLIBC_2.1' /usr/bin/ld: note:
'dlopen@@GLIBC_2.1' is defined in DSO /lib/i386-linux-gnu/libdl.so.2 so
try adding it to the linker command
line /lib/i386-linux-gnu/libdl.so.2: could not read symbols: Invalid
operation collect2: error: ld returned 1 exit status make[2]: ***
[utils/fgadmin/src/fgadmin] Error 1 make[1]: ***
[utils/fgadmin/src/CMakeFiles/fgadmin.dir/all] Error 2 make: *** [all]
Error 2
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
