On Thu, 2009-09-03 at 17:59 +0800 bob wrote: > If I just rewrite the version, gupnp-tools compiles fail. > I notice that it's rule is to get latest version from git server. > latest gupnp-tools version is 0.8 and depends gupnp 0.13. BUT latest gupnp > version is only 0.12.8. > Maybe get gupnp-tools version 0.7.1 could solve the problem. > "git clone git://git.gupnp.org/gupnp-tools" downloads latest(0.8) version... > But how to assign version 0.7.1??
You can tell jhbuild to checkout the specific git tag/branch in the moduleset file. Please refer to the 'gupnp' module in that file as an example: jhbuild checkout gupnp 0.12.8. > > ----- Original Message ----- > From: "Roger WANG" <[email protected]> > To: <[email protected]> > Sent: Thursday, September 03, 2009 5:19 PM > Subject: Re: [Moblin Dev] dependency issues from "jhbuild-moblin2 build" > > > > On Thu, 2009-09-03 at 15:35 +0800 bob wrote: > >> Hi All > >> > >> Another strange request from "jhbuild-moblin2 build"..... > >> It appears in configure upnp-tools stage, it ask me to have gupnp 0.13 > >> installed, but 0.12.8 is the latest release for all distribution. > >> How do you suggest to fix it? rewrite gupnp version from 0.12.8 to 0.13 > >> in > >> gupnp.pc??? > >> > > > > Maybe you could override the version of gupnp-tools to the same of > > gupnp (0.12.8) in the moduleset file. > > > > Override the dependency in the .pc file might not be good because > > it's actually 0.12.8, not 0.13. That would be a dirty hack. > > > >> > >> Thanks, > >> -Bob > >> > >> Below is full log : > >> *** Configuring gupnp-tools *** [22/30] > >> ./autogen.sh --prefix /root/moblin2/install --libdir > >> '/root/moblin2/install/lib' --disable-static --disable-gtk-doc > >> autoreconf: Entering directory `.' > >> autoreconf: configure.ac: not using Gettext > >> autoreconf: running: aclocal > >> autoreconf: configure.ac: tracing > >> autoreconf: running: libtoolize --copy > >> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac > >> and > >> libtoolize: rerunning libtoolize, to keep the correct libtool macros > >> in-tree. > >> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > >> autoreconf: running: /usr/bin/autoconf > >> autoreconf: running: /usr/bin/autoheader > >> autoreconf: running: automake --add-missing --copy --no-force > >> autoreconf: Leaving directory `.' > >> Copying file mkinstalldirs > >> Copying file po/Makefile.in.in > >> > >> Please add the files > >> codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 > >> progtest.m4 > >> from the /aclocal directory to your autoconf macro directory > >> or directly to your aclocal.m4 file. > >> You will also need config.guess and config.sub, which you can get from > >> ftp://ftp.gnu.org/pub/gnu/config/. > >> > >> configure: WARNING: unrecognized > >> options: --enable-debug, --disable-gtk-doc > >> checking for a BSD-compatible install... /root/.local/bin/install-check > >> checking whether build environment is sane... yes > >> checking for a thread-safe mkdir -p... /bin/mkdir -p > >> checking for gawk... gawk > >> checking whether make sets $(MAKE)... yes > >> checking whether to enable maintainer-specific portions of Makefiles... > >> yes > >> checking for style of include used by make... GNU > >> 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 dependency style of gcc... gcc3 > >> checking for library containing strerror... none required > >> checking for gcc... (cached) gcc > >> checking whether we are using the GNU C compiler... (cached) yes > >> checking whether gcc accepts -g... (cached) yes > >> checking for gcc option to accept ISO C89... (cached) none needed > >> checking dependency style of gcc... (cached) gcc3 > >> checking how to run the C preprocessor... gcc -E > >> 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 build system type... i686-pc-linux-gnu > >> checking host system type... i686-pc-linux-gnu > >> checking for a sed that does not truncate output... /bin/sed > >> checking for fgrep... /bin/grep -F > >> checking for ld used by gcc... /usr/i586-moblin-linux/bin/ld > >> checking if the linker (/usr/i586-moblin-linux/bin/ld) is GNU ld... yes > >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> checking whether ln -s works... yes > >> checking the maximum length of command line arguments... 1572864 > >> checking whether the shell understands some XSI constructs... yes > >> checking whether the shell understands "+="... yes > >> checking for /usr/i586-moblin-linux/bin/ld option to reload object > >> files... -r > >> checking for objdump... objdump > >> checking how to recognize dependent libraries... pass_all > >> checking for ar... ar > >> checking for strip... strip > >> checking for ranlib... ranlib > >> checking command to parse /usr/bin/nm -B output from gcc object... ok > >> 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 for dlfcn.h... yes > >> checking for objdir... .libs > >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> checking for gcc option to produce PIC... -fPIC -DPIC > >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> checking if gcc static flag -static works... yes > >> checking if gcc supports -c -o file.o... yes > >> checking if gcc supports -c -o file.o... (cached) yes > >> checking whether the gcc linker (/usr/i586-moblin-linux/bin/ld) supports > >> shared libraries... yes > >> checking whether -lc should be explicitly linked in... no > >> checking dynamic linker characteristics... GNU/Linux ld.so > >> checking how to hardcode library paths into programs... immediate > >> checking whether stripping libraries is possible... yes > >> checking if libtool supports shared libraries... yes > >> checking whether to build shared libraries... yes > >> checking whether to build static libraries... no > >> checking for stdlib.h... (cached) yes > >> checking for unistd.h... (cached) yes > >> checking for getpagesize... yes > >> checking for working mmap... yes > >> checking for pkg-config... /usr/bin/pkg-config > >> checking pkg-config is at least version 0.9.0... yes > >> checking for LIBGUPNP... configure: error: Package requirements > >> (gupnp-1.0 > >> >= 0.13) were not met: > >> > >> Requested 'gupnp-1.0 >= 0.13' but version of gupnp-1.0 is 0.12.8 > >> > >> Consider adjusting the PKG_CONFIG_PATH environment variable if you > >> installed software in a non-standard prefix. > >> > >> Alternatively, you may set the environment variables LIBGUPNP_CFLAGS > >> and LIBGUPNP_LIBS to avoid the need to call pkg-config. > >> See the pkg-config man page for more details. > >> > >> *** Error during phase configure of gupnp-tools: ########## Error running > >> ./autogen.sh --prefix /root/moblin2/install --libdir > >> '/root/moblin2/install/lib' --disable-static --disable-gtk-doc *** > >> [22/30] > >> > >> [1] Rerun phase configure > >> [2] Ignore error and continue to build > >> [3] Give up on module > >> [4] Start shell > >> [5] Reload configuration > >> [6] Go to phase "wipe directory and start over" > >> [7] Go to phase "clean" > >> [8] Go to phase "distclean" > >> choice: > >> > > _______________________________________________ > > Moblin dev Mailing List > > [email protected] > > > > To manage or unsubscribe from this mailing list visit: > > http://lists.moblin.org/listinfo/dev or your user account on > > http://moblin.org once logged in. > > > > For more information on the Moblin Developer Mailing lists visit: > > http://moblin.org/community/mailing-lists > _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
