In December version 1.5.0 of fgrun was released to keep in sync with the release of flightgear 1.9.0. Currently on fgrun 1.0.0 is available in portage. I copied the 1.0.0 ebuild to my overlay but this failed to work since the fltk patch would not apply. I have a working fltk patch that I will attach to this bug report. Reproducible: Always
Created attachment 178623 [details, diff] fgrun-1.5.0-fltk.patch
this is needed to --- configure.ac.old 2007-04-25 22:26:19.000000000 +0200 +++ configure.ac 2007-04-25 22:27:41.000000000 +0200 *************** *** 116,116 **** --- 116,117 ---- -XX_PATH_PLIB(1.8.0) +XX_PATH_PLIB=(1.8.0) and cleaning tarbal. its full of junk and. It works with both packes and cleaned tarbal on my amd64 and fgrun 1.5.1
Reason of plib patch ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for ranlib... ranlib checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for boostlib >= 1.34.0... yes checking for cos in -lm... yes checking for an ANSI C-conforming const... yes checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for XCreateWindow in -lX11... yes checking for XShmCreateImage in -lXext... yes checking for XGetExtensionVersion in -lXi... yes checking for IceOpenConnection in -lICE... yes checking for SmcOpenConnection in -lSM... yes checking for XtMalloc in -lXt... yes checking for XmuLookupStandardColormap in -lXmu... yes checking for library containing glNewList... -lGL checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether time.h and sys/time.h may both be included... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking libutil.h usability... no checking libutil.h presence... no checking for libutil.h... no checking pty.h usability... yes checking pty.h presence... yes checking for pty.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking utmp.h usability... yes checking utmp.h presence... yes checking for utmp.h... yes checking util.h usability... no checking util.h presence... no checking for util.h... no checking windows.h usability... no checking windows.h presence... no checking for windows.h... no checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for gzopen in -lz... yes ./configure: line 8337: syntax error near unexpected token `1.8.0' ./configure: line 8337: `XX_PATH_PLIB(1.8.0)'
Created attachment 203850 [details, diff] Patch fgrun-1.0.0.ebuild to fgrun-1.5.1.ebuild Version 1.5.1 also released Jan 26 2009, that drops gcc43.patch requirement (first change in my patch). The patch from comment 2 should probably be in --unified format. Patch lines are same for 1.5.0 and 1.5.1. My patch also fixes two src_prepare() -functions typo, which leaves first to not be executed at all. Second should be src_configure(). Fixes QA notice from beginning of compile. This probably should fix bug 258405 too (where a fix was proposed, but I doubt it would remove the QA at all).
Wonderful! It works. Thanks (In reply to comment #4) > Created an attachment (id=203850) [edit] > Patch fgrun-1.0.0.ebuild to fgrun-1.5.1.ebuild > > Version 1.5.1 also released Jan 26 2009, that drops gcc43.patch requirement > (first change in my patch). The patch from comment 2 should probably be in > --unified format. Patch lines are same for 1.5.0 and 1.5.1. > My patch also fixes two src_prepare() -functions typo, which leaves first to > not be executed at all. Second should be src_configure(). Fixes QA notice from > beginning of compile. This probably should fix bug 258405 too (where a fix was > proposed, but I doubt it would remove the QA at all). >
Created attachment 206626 [details] fgrun-1.5.1.ebuild with previous patch and fltk-requirement fix Since fltk upgraded to 1.1.9 fgrun needs +threads useflag from fltk to compile. This ebuild includes my previous patch and the fltk[threads]-requirement. If fltk:1.1 (>=1.1.9) is built without threads-support, linking fgrun will fail as fltk-libs don't contain locking-abilities.
I've just added it in cvs, thanks everyone!
