Re: F-Spot from CVS not autogen'ing

[Stephane Delcroix <stephane delcroix org>]

This time, I'll learn you how to fish...

there's a nice tool in debian/ubuntu called apt-file.

install it like this:

apt-get install apt-file

then, update its database, by running, as root

apt-file update

then, when you're looking for a file called afile, you can find in which
package it belongs by running

apt-file search afile

So, the Syste.Runtime.Remoting.dll file is in the package
libmono-system-runtime2.0-cil

btw, there's an almost up-to-date page in the f-spot wiki on how to
install CVS or released version, focused on ubuntu...

regards

s


On Tue, 2006-12-19 at 13:21 +0200, Dotan Cohen wrote:
> On 19/12/06, Stephane Delcroix <stephane delcroix org> wrote:
> > Hi Dotan,
> >
> > I said:
> > > > install intltoolize form the intltool package in ubuntu
> >
> > meaning installing the intltool package containing the intltoolize util.
> > Or, in a more debian/ubuntu way:
> >
> > apt-get install intltool
> >
> > regards
> >
> > s
> 
> Hehe, thanks. I wonder why apt-cache didn't find it then. Anyway, it's
> now installed via apt-get. Once again I feel the n00b juices flowing.
> 
> However, autogen is _still_ not finishing. It complains about these:
> checking for working makeinfo... missing
> --snip--
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt...
> 
> I searched apt-cache for makeinfo, but found no relevant package for
> that either. G77, F77, and some others were available, should I
> install them even though I have gcc? The full output is:
> dotancohen ubuntu:~/bin/development/f-spot/f-spot$ ./autogen.sh
> --prefix=/home/dotancohen/bin/unstable/f-spot
> processing .
> Creating ./aclocal.m4 ...
> Running gettextize...  Ignore non-fatal messages.
> 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 /usr/share/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/.
> 
> Making ./aclocal.m4 writable ...
> Running intltoolize...
> Running libtoolize...
> Running aclocal  ...
> Running autoheader...
> Running automake --gnu  ...
> tools/Makefile.am:4: variable `NULL' not defined
> tools/Makefile.am:4: variable `NULL' not defined
> Running autoconf ...
> Running ./configure --enable-maintainer-mode --enable-compile-warnings
> --prefix=/home/dotancohen/bin/unstable/f-spot ...
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets $(MAKE)... yes
> checking for working aclocal-1.4... found
> checking for working autoconf... found
> checking for working automake-1.4... found
> checking for working autoheader... found
> checking for working makeinfo... missing
> checking whether to enable maintainer-specific portions of Makefiles... yes
> checking for intltool >= 0.21... 0.35.0 found
> checking for perl... /usr/bin/perl
> checking for XML::Parser... ok
> checking for iconv... /usr/bin/iconv
> checking for msgfmt... /usr/bin/msgfmt
> checking for msgmerge... /usr/bin/msgmerge
> checking for xgettext... /usr/bin/xgettext
> 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 library containing strerror... none required
> 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 ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> 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 dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether  accepts -g... no
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... cat:
> /etc/ld.so.conf.d/*.conf: No such file or directory
> 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... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
> checking dynamic linker characteristics... cat:
> /etc/ld.so.conf.d/*.conf: No such file or directory
> GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> ./configure: line 19730: GNOME_COMPILE_WARNINGS: command not found
> checking for pkg-config... /usr/bin/pkg-config
> checking for GLIB - version >= 2.0.0... yes (version 2.12.4)
> checking for mono... /usr/bin/mono
> checking for gmcs... /usr/bin/gmcs
> checking for mono.pc... found
> checking for Mono.Data.SqliteClient.dll... found
> checking for Mono.Posix.dll... found
> checking for System.Runtime.Remoting.dll... configure: error: missing
> required mono 2.0 DLL: System.Runtime.Remoting.dll
> 
> Dotan Cohen
> 
> http://technology-sleuth.com/short_answer/what_is_a_router.html
> http://what-is-what.com/what_is/xhtml.html
> 
-- 
Stephane Delcroix
stephane delcroix org