EyeOfGnome Plugins

[Vistaus]

Ik probeer de plugins voor EyeOfGnome te installeren maar het gaat niet helemaal goed.

Ik doe precies wat er staat. Er staat:

Code: [Selecteer]

./autogen.sh --prefix=$HOME/.gnome2/Dus dat doe ik en dan krijg ik de melding:

Code: [Selecteer]

You need to install gnome-common from the GNOME SubversionDus ik heb gnome-common probleemloos uit de SVN geinstalleerd maar toch krijg ik elke keer weer dezelfde melding als ik "./autogen.sh" enz. intyp.

Wat gaat er fout?

[Gijsbert]

Heb je al het bestand uitvoer baar gemaakt?
chmod +x /home/Vistaus/Desktop/autogen.sh als het daar staat anders moet je het juiste pad/benaming aanpassen.
En dan sh ./autogen.sh --prefix=$HOME/.gnome2/ lukt dit?

Met vriendelijke groet,

Gijs

[Vistaus]

Het bestand was al uitvoerbaar ja

En nee, hij blijft nog steeds vragen om gnome-common uit de SVN.

[Prosper]

Vistaus, ik heb dat ook eens geprobeerd en hij geeft dezelfde foutmelding.  Jelaas heb ik er geen flauw idee van hoe je dan gnome-common installert vanuit de svn-repo..  Als je dat nu eens uitlegde, dan kan ik het nog eens proberen..

[Vistaus]

The best solution depends on what you want to do. If you want to keep up with all the latest GNOME work then a full SVN build is best. If you only want to work on Gnome Games then it is best only to download the single module. To do this issue the following shell commands from the directory you want to store everything in.

$ svn co http://svn.gnome.org/svn/gnome-common/trunk gnome-common

Go into the gnome-common directory and type ./autogen.sh --prefix=/some/directory, this will run configure and set everything up. The directory you give should be the place you want to install the GNOME software you are going to hack on. This should not be /usr. You can use your home directory, e.g. --prefix=~/gnome/.

If autogen.sh complains about missing libraries or libraries that are too old then you will need to find and install appropriate versions of these libraries yourself. Usually these can be found at the GNOME FTP site. If autogen.sh dies strangely then either you haven't installed gnome-common or you need to install newer autotools. Once autogen.sh has run successfully you can type make install to build everything and install it.

[Vistaus]

Nog niemand die het gelukt is?

[Vistaus]

Nog steeds niemand? Ik zou graag de plugins willen gebruiken..

[Vistaus]

Niemand?

[Gijsbert]

Ik ga het even proberen, ben zo terug

[Vistaus]

Ok alvast bedankt

[Gijsbert]

Sorry voor het wachten. Oke gaat ie:
Ga in een directory staan met de terminal waar je de map gnome wilt hebben bijv Downloads doe dit
gijs@gijs-desktop:~/Downloads$ sudo svn co http://svn.gnome.org/svn/gnome-common/trunk gnome-common mocht je nog svn moeten installeren wordt dat aangegeven. Deze installeren en dan het commando opnieuw uitvoeren.
Vervolgens naar de map gnome-common gaan die dus in Downloads staat, kan bij jouw een andere zijn, en dit commando gijs@gijs-desktop:~/Downloads/gnome-common$ sudo ./autogen.sh --prefix=/home/gijs
Krijg je dit, moet je alleen een beetje aan het eind het commando make ingeven zie je vanzelf:

Code: [Selecteer]

gijs@gijs-desktop:~/Downloads/gnome-common$ sudo ./autogen.sh --prefix=/home/gijs
[sudo] password for gijs:
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.61
checking for automake >= 1.9...
  testing automake-1.10... found 1.10.1
Checking for forbidden M4 macros...
Processing ./configure.in
Running aclocal-1.10...
Running autoconf...
Running automake-1.10...
configure.in:7: installing `./install-sh'
configure.in:7: installing `./missing'
Makefile.am: installing `./INSTALL'
Makefile.am: installing `./COPYING'
Running ./configure --enable-maintainer-mode --prefix=/home/gijs ...
checking for a BSD-compatible install... /usr/bin/install -c
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
configure: creating ./config.status
config.status: creating Makefile
config.status: creating gnome-common.spec
config.status: creating macros2/Makefile
config.status: creating doc-build/Makefile
config.status: creating doc-build/gnome-doc-common
Now type `make' to compile Gnome Common Macros
gijs@gijs-desktop:~/Downloads/gnome-common$ make
Making all in macros2
make[1]: Map '/home/gijs/Downloads/gnome-common/macros2' wordt binnengegaan
make[1]: Er hoeft niets gedaan te worden voor 'all'.
make[1]: Map '/home/gijs/Downloads/gnome-common/macros2' wordt verlaten
Making all in doc-build
make[1]: Map '/home/gijs/Downloads/gnome-common/doc-build' wordt binnengegaan
make[1]: Er hoeft niets gedaan te worden voor 'all'.
make[1]: Map '/home/gijs/Downloads/gnome-common/doc-build' wordt verlaten
make[1]: Map '/home/gijs/Downloads/gnome-common' wordt binnengegaan
make[1]: Er hoeft niets gedaan te worden voor 'all-am'.
make[1]: Map '/home/gijs/Downloads/gnome-common' wordt verlaten
gijs@gijs-desktop:~/Downloads/gnome-common$Met vriendelijke groet,

Gijs

[Vistaus]

Ga ik proberen, je hoort zo wel de uitkomst. Bedankt zover

[Vistaus]

Weer niet gelukt. De plugins blijven maar vragen om gnome-common uit de svn.

Edit: Moest nog make install doen. Nu lukt het wel. Maar nu krijg ik weer de melding dat intltool te oud is. Ik moet versie 0.35.0 of hoger hebben. Maar ik heb intltool 0.40.1

[Gijsbert]

Vistaus, kan je de uitkomst van de terminal commando's hier kopiëren en plakken?
Kan ik even mee kijken.

Met vriendelijke groet,

Gijs

[Vistaus]

Hier de uitkomst:

Code: [Selecteer]

heimen-at-ubuntu@heimen-at-compaq:~$ cd .gnome2
heimen-at-ubuntu@heimen-at-compaq:~/.gnome2$ ln -s . lib
ln: creating symbolic link `lib/.': File exists
heimen-at-ubuntu@heimen-at-compaq:~/.gnome2$ cd eog-plugins
heimen-at-ubuntu@heimen-at-compaq:~/.gnome2/eog-plugins$ cd trunk
heimen-at-ubuntu@heimen-at-compaq:~/.gnome2/eog-plugins/trunk$ ./autogen.sh --prefix=$HOME/.gnome2
/home/heimen-at-ubuntu/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... found 2.61
checking for automake >= 1.9...
  testing automake-1.10... found 1.10.1
checking for libtool >= 1.4.3...
  testing libtoolize... found 1.5.26
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.16.4
checking for intltool >= 0.25...
  testing intltoolize... found 0.40.1
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.22
checking for gnome-doc-utils >= 0.4.2...
  testing gnome-doc-prepare... found 0.12.2
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing ./configure.ac
Running libtoolize...
Running glib-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 /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/.

Running intltoolize...
Running gnome-doc-prepare...
You should update your 'aclocal.m4' by running aclocal.
Running aclocal-1.10...
/usr/share/aclocal/gtk--.m4:10: warning: underquoted definition of AM_PATH_GTKMM
/usr/share/aclocal/gtk--.m4:10:   run info '(automake)Extending aclocal'
/usr/share/aclocal/gtk--.m4:10:   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
Running autoconf2.50...
Running autoheader2.50...
Running automake-1.10...
plugins/postr/Makefile.am:24: `%'-style pattern rules are a GNU make extension
plugins/postr/Makefile.am:24: wildcard $(top_srcdir: non-POSIX variable name
plugins/postr/Makefile.am:24: (probably a GNU make extension)
Running ./configure --enable-maintainer-mode --prefix=/home/heimen-at-ubuntu/.gnome2 ...
checking for a BSD-compatible install... /usr/bin/install -c
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 build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
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 recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... 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 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 dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 98304
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... 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
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... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
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 for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for intltool >= 0.35.0... awk: cmd. line:1: fatal: cannot open file `./intltool-update.in' for reading (No such file or directory)
awk: cmd. line:1: fatal: cannot open file `./intltool-update.in' for reading (No such file or directory)
 found
./configure: line 22525: test: : integer expression expected
configure: error: Your intltool is too old.  You need intltool 0.35.0 or later.
heimen-at-ubuntu@heimen-at-compaq:~/.gnome2/eog-plugins/trunk$

[Sjoerd Broekhuijsen]

probeer anders eens
sudo apt-get install intltool-debian

Ik zag nl 2 pakketen toen ik in synaptic keek, intltool en intltool-debian...
Mischien heb je intltool-debian nodig ofzo :S?

[Vistaus]

Ik denk het niet, dan zou ie dat wel aangeven.

Kleine correctie: Ik heb niet intltool 0.40.1 maar intltool 0.37.1. En intltool-debian is 0.35.0, hoog genoeg dus voor de plugins.

[Vistaus]

Ik heb het voor alle zekerheid nog even opgezocht en het inderdaad intltool en niet intltool-debian.

[Vistaus]

Ik heb een debje van intltool 0.40.0-1 uit Inteprid gehaald (niet uit Inteprid zelf, maar hij is te vinden in Inteprid en heb hem via Launchpad binnengehaald) en nu is het keurig geinstalleerd.

Iedereen weer bedankt

Weet iemand trouwens de website van intltool? Of een plek waar ik nieuwe en oude versies van intltool kan vinden?