On Mon, 16 Jul 2007 13:21:10 +0200, Harold Aling h.aling@home.nl wrote:
On Mon, 16 Jul 2007 11:25:21 +0200, Enrico Tröger enrico.troeger@uvena.de wrote:
On Mon, 16 Jul 2007 9:47:15 +0200, Harold Aling h.aling@home.nl wrote:
Hi,
I can't seem to compile the latest svn revisions of Geany. The last one I could compile was r1687.
The error: /bin/sh ../libtool --silent --mode=link i486-linux-gnu-gcc -g -DGEANY_DEBUG -Wall -g -O2 -Wl,-z,defs -o geany about.o build.o callbacks.o dialogs.o document.o editor.o encodings.o filetypes.o highlighting.o interface.o keybindings.o keyfile.o main.o msgwindow.o navqueue.o notebook.o plugins.o prefs.o project.o sciwrappers.o search.o socket.o support.o symbols.o templates.o tools.o treeviews.o ui_utils.o utils.o vte.o ../scintilla/libscintilla.a ../tagmanager/libtagmanager.a -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXfixes -lpango-1.0 -lcairo -lX11 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lCrun /usr/bin/ld: cannot find -lCrun collect2: ld returned 1 exit status make[3]: *** [geany] Error 1 make[3]: Leaving directory `/home/harold/svn/geany-0.12-svn1702/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/harold/svn/geany-0.12-svn1702' make[1]: *** [all-recursive-am] Error 2 make[1]: Leaving directory `/home/harold/svn/geany-0.12-svn1702' make: *** [build-stamp] Error 2
My bad or buggy?
Maybe buggy. Did you (or the autotools) run autoconf after updating to SVN >= r1689? Just to get sure: run autogen.sh in the Geany source directory. If the build still fails after it, it is most probably a bug.
I've got myself a clean SVN checkout, ran autogen.sh and tried to build Geany again -> same error.
The problem is the build system guesses you don't have a gcc and so it uses build flags(esp. linker flag -lCrun) which are mostly for Solaris. Will be fixed soon. As a workaround, configuring Geany with: CC=gcc ./configure should help.
If I can find the time, I'll try to find out since which revision this error occurs.
Np need to, it is since r1689.
Regards, Enrico