Hi,
I've been compiling & using latest SVN version for quite a long time now. Recently *something* has changed and I can not compile it the usual way on this PC. configure runs OK, but the later parts of make stop with error.
Here are the first error message lines:
/bin/bash ../libtool --silent --mode=link gcc -g -DGEANY_DEBUG -g -O2 -o geany about.o build.o callbacks.o dialogs.o document.o editor.o encodings.o filetypes.o geanyobject.o geanywraplabel.o highlighting.o interface.o keybindings.o keyfile.o main.o msgwindow.o navqueue.o notebook.o plugins.o prefix.o prefs.o printing.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 ../scintilla/libscintilla.a(ScintillaGTK.o): In function `ScintillaGTK::Copy()': /home/kilo/SVN/geany/scintilla/ScintillaGTK.cxx:1314: undefined reference to `operator new(unsigned int)'
And many more similar ones follow, complaining about operator new, delete...
using Ubuntu Feisty Fawn libtool 1.5.22-4 gcc 4.1.2-1 g++ 4.1.2-1
I've attached the complete make log. What can be the problem?
Thanks
kilo Gabor Kmetyko
On Fri, 22 Feb 2008 10:19:08 +0100, kilo kg_kilo@freemail.hu wrote:
Hi,
I've been compiling & using latest SVN version for quite a long time now. Recently *something* has changed and I can not compile it the usual way on this PC. configure runs OK, but the later parts of make stop with error. [...] I've attached the complete make log. What can be the problem?
the problem is that the geany executable is linked with gcc (the C compiler) but it has to be linked with g++ (the C++ compiler) because it will contain C++ code. The question is why it doesn't link anymore with g++. It's probably because of commit of SVN r2268.
Could you try to update and build SVN r2271? If it fails again, please do the following steps (in the top source directory):
make distclean ./autogen.sh make
Regards, Enrico
On Fri, Feb 22, 2008 at 11:14 AM, Enrico Tröger enrico.troeger@uvena.de wrote:
On Fri, 22 Feb 2008 10:19:08 +0100, kilo kg_kilo@freemail.hu wrote:
Could you try to update and build SVN r2271? If it fails again, please do the following steps (in the top source directory):
make distclean ./autogen.sh make
Regards, Enrico
Hi Enrico,
tried both methods but no success, same error messages.
I may have been too obscure, the last version I've successfully built was r1939, in October. However I can compile latest versions on my home PCs, using Ubuntu Gutsy.
Any further hints? Or fall back to using released version?
Thanks
kilo
Hi Kilo,
On Fri, Feb 22, 2008 at 2:32 PM, kilo kg_kilo@freemail.hu wrote:
tried both methods but no success, same error messages.
I may have been too obscure, the last version I've successfully built was r1939, in October. However I can compile latest versions on my home PCs, using Ubuntu Gutsy.
Any further hints? Or fall back to using released version?
Can you try using a fresh checkout?
I use Feisty and Gusty and everything works like a charm using the current trunk.
Cheers,
On Fri, 22 Feb 2008 14:51:40 +0100, Pierre Joye pierre.php@gmail.com wrote:
Hi Kilo,
On Fri, Feb 22, 2008 at 2:32 PM, kilo kg_kilo@freemail.hu wrote:
tried both methods but no success, same error messages.
I may have been too obscure, the last version I've successfully built was r1939, in October. However I can compile latest versions on my home PCs, using Ubuntu Gutsy.
Any further hints? Or fall back to using released version?
Can you try using a fresh checkout?
It does make sense to checkout the sources into a separate directory than you are compiling from. SVN has a command export to make a clean copy of the sources (without .svn-dirs and so on).
For example something like this:
mkdir ~/projects/ cd projects svn checkout https://geany.svn.sourceforge.net/svnroot/geany/trunk geany svn export geany geany-0.14svn # do this everytime you make a new compile, delete the old geany-0.14svn before cd geany-0.14svn # here youre compile commands
I'm building RPM-Packages on my own on my Fedora 8 System and this works perfect with every revision from SVN :)
I use Feisty and Gusty and everything works like a charm using the current trunk.
Cheers,
On Fri, Feb 22, 2008 at 8:45 PM, Dominic Hopf dmaphy_damastasif@gmx.net wrote:
On Fri, 22 Feb 2008 14:51:40 +0100, Pierre Joye pierre.php@gmail.com wrote:
Hi Kilo,
On Fri, Feb 22, 2008 at 2:32 PM, kilo kg_kilo@freemail.hu wrote:
tried both methods but no success, same error messages.
I may have been too obscure, the last version I've successfully built was r1939, in October. However I can compile latest versions on my home PCs, using Ubuntu Gutsy.
Any further hints? Or fall back to using released version?
Can you try using a fresh checkout?
It does make sense to checkout the sources into a separate directory than you are compiling from. SVN has a command export to make a clean copy of the sources (without .svn-dirs and so on).
For example something like this:
mkdir ~/projects/ cd projects svn checkout https://geany.svn.sourceforge.net/svnroot/geany/trunk geany svn export geany geany-0.14svn # do this everytime you make a new compile, delete the old geany-0.14svn before cd geany-0.14svn # here youre compile commands
You can build outside the src tree, only the auto* crap has to be in the original directory. But then you can do:
cd geany_bld /path/to/geany_src/configure ... make
I did it not try it with geany, it is possible to have some issues in the various AC macros (relative paths used instead of having top directory, etc.).
Did I mention that I love CMake? (Which supports that by default and is crossplatform :-)
Cheers,
Hi
On Fri, 2008-02-22 at 21:04 +0100, Pierre Joye wrote:
Did I mention that I love CMake? (Which supports that by default and is crossplatform :-)
I am yet to see any autotools replacement that doesn't suck one way or another. So don't insult our favorite tool. ;-)
Best regards, Yura Siamashka
On Fri, 22 Feb 2008 23:06:25 +0200, Yura Siamashka yurand2@gmail.com wrote:
Hi
On Fri, 2008-02-22 at 21:04 +0100, Pierre Joye wrote:
Did I mention that I love CMake? (Which supports that by default and is crossplatform :-)
I am yet to see any autotools replacement that doesn't suck one way or another. So don't insult our favorite tool. ;-)
;-).
Regards, Enrico
On Fri, 22 Feb 2008 21:04:18 +0100, "Pierre Joye" pierre.php@gmail.com wrote:
Did I mention that I love CMake? (Which supports that by default and is crossplatform :-)
Me too. Two years ago, I did some testing with CMake and it's great. But there were a few problems when writing a CMakeLists.txt. Also, at this time there were no way of detecting an installed GTK 2.0 environment. One had to write the code manually. I think(hope) this is fixed in the meantime. But there is still another problem with CMake: it is another dependency for Geany. Compared to autotools, you need to install cmake in order to build Geany. Autotools doesn't require to install anything except a shell interpreter for the configure script. This is the main reason why I don't work on CMake support although I really like it.
scons has the same problem.
Regards, Enrico
On Fri, Feb 22, 2008 at 2:51 PM, Pierre Joye pierre.php@gmail.com wrote:
Can you try using a fresh checkout?
Hi Pierre,
I've already tried fresh checkouts several times but it didn't help.
Thanks
kilo
On Fri, Feb 22, 2008 at 3:19 AM, kilo kg_kilo@freemail.hu wrote:
Here are the first error message lines: /home/kilo/SVN/geany/scintilla/ScintillaGTK.cxx:1314: undefined reference to `operator new(unsigned int)'
And many more similar ones follow, complaining about operator new, delete...
maybe try:
% make LDFLAGS=-lstdc++
- Jeff
On Sat, Feb 23, 2008 at 1:25 AM, Jeff Pohlmeyer yetanothergeek@gmail.com wrote:
maybe try:
% make LDFLAGS=-lstdc++
- Jeff
Hi Jeff,
will try it Monday.
Thanks
kilo
On Sat, Feb 23, 2008 at 1:25 AM, Jeff Pohlmeyer yetanothergeek@gmail.com wrote:
maybe try:
% make LDFLAGS=-lstdc++
- Jeff
And the award goes to... Jeff!
Made a clean new checkout, called autogen.sh with the above option and voilá it worked smooth & nice.
Thanks Jeff and all the others who have helped.
kilo Gabor Kmetyko
On Mon, 25 Feb 2008 10:55:48 +0100, kilo kg_kilo@freemail.hu wrote:
On Sat, Feb 23, 2008 at 1:25 AM, Jeff Pohlmeyer yetanothergeek@gmail.com wrote:
maybe try:
% make LDFLAGS=-lstdc++
- Jeff
And the award goes to... Jeff!
Made a clean new checkout, called autogen.sh with the above option and voilá it worked smooth & nice.
But the question remains: why doesn't it work without this library on your system? Or why does it work without on some systems?
Regards, Enrico