[Monetdb-developers] bootstrapping problems on HEAD
Hi All, Here in Twente on our SuSe systems we are currently experiencing 2 problems with the HEAD of pathfinder. 1) Installing buildtools fails because mel is not handled automatically anymore. We have to go to mel and bootstrap-configure by hand. Then we can handle the rest of the buildtools. Did we miss something? 2) We are experiencing problems with the version of autoconf on SuSe10.0. Bootstrap wants to run at least 2.57 but we are running 2.59 so this should be OK: LOG: monetdb/MonetDB> autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. monetdb/MonetDB> ./bootstrap automake 1.9.6 is 1.7 or newer. Good. autoconf is older than 2.57. We require (at least) autoconf 2.57. Please get a newer version (cf. http://www.gnu.org/software/autoconf/). monetdb/MonetDB> Jan Flokstra.
On Fri, Jan 12, 2007 at 02:14:17PM +0100, Jan Flokstra wrote:
Hi All,
Here in Twente on our SuSe systems we are currently experiencing 2 problems with the HEAD of pathfinder.
1) Installing buildtools fails because mel is not handled automatically anymore. We have to go to mel and bootstrap-configure by hand. Then we can handle the rest of the buildtools. Did we miss something?
with up-to-date sources and clean build from scratch? work fine for me and testing (cf. http://monetdb.cwi.nl/Development/TestWeb/Current/buildtools/index.html)
2) We are experiencing problems with the version of autoconf on SuSe10.0. Bootstrap wants to run at least 2.57 but we are running 2.59 so this should be OK:
LOG:
monetdb/MonetDB> autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille.
Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. monetdb/MonetDB> ./bootstrap automake 1.9.6 is 1.7 or newer. Good. autoconf is older than 2.57. We require (at least) autoconf 2.57. Please get a newer version (cf. http://www.gnu.org/software/autoconf/). monetdb/MonetDB>
what does autoconf --version 2>/dev/null | sed -n -e '/^[Aa]utoconf/{s/.* //g;s/-.*//g;p;q;}' say? Stefan
Jan Flokstra.
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
On Friday 12 January 2007 14:20, Stefan Manegold wrote:
On Fri, Jan 12, 2007 at 02:14:17PM +0100, Jan Flokstra wrote:
Hi All,
Here in Twente on our SuSe systems we are currently experiencing 2 problems with the HEAD of pathfinder.
1) Installing buildtools fails because mel is not handled automatically anymore. We have to go to mel and bootstrap-configure by hand. Then we can handle the rest of the buildtools. Did we miss something?
with up-to-date sources and clean build from scratch?
work fine for me and testing (cf. http://monetdb.cwi.nl/Development/TestWeb/Current/buildtools/index.html)
I do think something is wrong with configure. It happens on all our machines. All with a clean prefix and fresh buildtools I removed the prefix and checked in a fresh buildtools. Attached is the log of the build. JanF.
On 12-01-2007 14:39:47 +0100, Jan Flokstra wrote:
I do think something is wrong with configure. It happens on all our machines.
Indeed. It looks like configure for mel isn't run.
[1mewi865[0m software/buildtools> ./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[A[29G2 --enable-pftijah=yes[K[80G t[K[A[51G[29G./bootstrap[K[29G2 --enable-pftijah=yes[29G./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[K[K[K[K[K[K[K[K[K[K[K[K[K--enable-oid32 --enable-pftijah=yes
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
On Friday 12 January 2007 14:50, Fabian Groffen wrote:
On 12-01-2007 14:39:47 +0100, Jan Flokstra wrote:
I do think something is wrong with configure. It happens on all our machines.
Indeed. It looks like configure for mel isn't run.
[1mewi865[0m software/buildtools> ./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[A[29G2 --enable-pftijah=yes[K[80G t[K[A[51G[29G./bootstrap[K[29G2 --enable-pftijah=yes[29G./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[K[K[K[K[K[K[K[K[K[K[K[K[K--enable -oid32 --enable-pftijah=yes
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
Yes. It is a bit screwed up by typescript!
On 12-01-2007 14:54:17 +0100, Jan Flokstra wrote:
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
Yes. It is a bit screwed up by typescript!
I found the problem. The workaround is to configure/build in a separate directory, till I find the proper fix.
On 12-01-2007 14:58:02 +0100, Fabian Groffen wrote:
On 12-01-2007 14:54:17 +0100, Jan Flokstra wrote:
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
Yes. It is a bit screwed up by typescript!
I found the problem. The workaround is to configure/build in a separate directory, till I find the proper fix.
Or use an absolute path to call configure...
Jan, thanks for reporting. It should be fixed now in CVS. At least for my own attempt it configured and maked without a problem now. On 12-01-2007 15:00:52 +0100, Fabian Groffen wrote:
On 12-01-2007 14:58:02 +0100, Fabian Groffen wrote:
On 12-01-2007 14:54:17 +0100, Jan Flokstra wrote:
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
Yes. It is a bit screwed up by typescript!
I found the problem. The workaround is to configure/build in a separate directory, till I find the proper fix.
Or use an absolute path to call configure...
On 2007-01-12 14:50, Fabian Groffen wrote:
On 12-01-2007 14:39:47 +0100, Jan Flokstra wrote:
I do think something is wrong with configure. It happens on all our machines.
Indeed. It looks like configure for mel isn't run.
[1mewi865[0m software/buildtools> ./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[A[29G2 --enable-pftijah=yes[K[80G t[K[A[51G[29G./bootstrap[K[29G2 --enable-pftijah=yes[29G./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[K[K[K[K[K[K[K[K[K[K[K[K[K--enable-oid32 --enable-pftijah=yes
Is your final configure call --prefix=/usr/local/flokstra --enable-bits=64 --enable-oid32 --enable-pftijah=yes here?
Doesn't really matter. It seems to key point is that Jan runs configure in the source directory. We always use a separate build directory. When I try configure in the source directory (after bootstrap) I see the following lines: mkdir: cannot create directory `mel': File exists ./configure: line 1807: ./mel/configure: No such file or directory -- Sjoerd Mullender
On Friday 12 January 2007 15:00, Sjoerd Mullender wrote: [...]
Doesn't really matter. It seems to key point is that Jan runs configure in the source directory. We always use a separate build directory.
When I try configure in the source directory (after bootstrap) I see the following lines:
mkdir: cannot create directory `mel': File exists ./configure: line 1807: ./mel/configure: No such file or directory
OK, this is the problem! But I (and most of the people here) have compiled Pathfinder this way for years and it always worked. It is only very recently (last week) that it fails. But we will bootstrap mel by hand and wait for a fix. The other (autogen) problem was caused by a sick system. The line you gave me worked half of the time and half of the time there was no output: Ok er is iets goed mis met mijn systeem en ik ga voor de herstart: Zie deze log: monetdb/MonetDB> autoconf --version | sed -n -e '/^[Aa]utoconf/{s/.* //g;s/-.*//g;p;q;}' monetdb/MonetDB> autoconf --version | sed -n -e '/^[Aa]utoconf/{s/.* //g;s/-.*//g;p;q;}' 2.59 We rebooted and it works fine now, JanF.
On Fri, Jan 12, 2007 at 02:39:47PM +0100, Jan Flokstra wrote:
On Friday 12 January 2007 14:20, Stefan Manegold wrote:
On Fri, Jan 12, 2007 at 02:14:17PM +0100, Jan Flokstra wrote:
Hi All,
Here in Twente on our SuSe systems we are currently experiencing 2 problems with the HEAD of pathfinder.
1) Installing buildtools fails because mel is not handled automatically anymore. We have to go to mel and bootstrap-configure by hand. Then we can handle the rest of the buildtools. Did we miss something?
with up-to-date sources and clean build from scratch?
work fine for me and testing (cf. http://monetdb.cwi.nl/Development/TestWeb/Current/buildtools/index.html)
I do think something is wrong with configure. It happens on all our machines. All with a clean prefix and fresh buildtools I removed the prefix and checked in a fresh buildtools. Attached is the log of the build.
JanF.
Script started on Fri 12 Jan 2007 02:23:04 PM CET [1mewi865[0m flokstra/software> cvs -d:ext:jflokstra@monetdb.cvs.sourceforge.net:/cvsr oot/monetdb co buildtools jflokstra@monetdb.cvs.sourceforge.net's password: cvs checkout: Updating buildtools [...] [1mewi865[0m flokstra/software> ls /usr/local/flokstra [00m[01;34msoftware[00m [m[1mewi865[0m flokstra/software> cd buildtools Directory: /usr/local/flokstra/software/buildtools [1mewi865[0m software/buildtools> ./bootstrap configure.ac: installing `./install-sh' configure.ac: installing `./missing' Makefile.am: installing `./INSTALL' Makefile.am: installing `./depcomp' configure.ac: installing `./install-sh' configure.ac: installing `./missing' Makefile.am: installing `./INSTALL' Makefile.am: installing `./depcomp' configure.ac: installing `./install-sh' configure.ac: installing `./missing' Makefile.am: installing `./INSTALL' Makefile.am: installing `./depcomp' configure.ac: installing `./install-sh' configure.ac: installing `./missing' Makefile.am: installing `./INSTALL' [1mewi865[0m software/buildtools> ./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[A[29G2 --enable-pftijah=yes[K[80G t[K[A[51G[29G./bootstrap[K[29G2 --enable-pftijah=yes[29G./configure --prefix=/usr/local/flokstra --enable-bi ts=64 --enable-oid3[K[K[K[K[K[K[K[K[K[K[K[K[K--enable-oid32 --enable-pftijah=yes
You actually run configure (and hence make) in your source tree, i.e., do not use a separate build directory --- I have to admit, I never tested that (though it should work) --- I (and testing) alwasy use a separate build directory, basically because this keep the source tree clean from any "build-junk", and hence allows to clean the build tree with a simple `rm -rf` ... using a separate build dir just works fine for me ... Stefan [...]
[1mewi865[0m software/buildtools> make [...] make[2]: Leaving directory `/usr/local/flokstra/software/buildtools/Mx' Making all in mel make[2]: Entering directory `/usr/local/flokstra/software/buildtools/mel' make[2]: *** No rule to make target `all'. Stop. make[2]: Leaving directory `/usr/local/flokstra/software/buildtools/mel' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/flokstra/software/buildtools' make: *** [all] Error 2 [1mewi865[0m software/buildtools> ^Dexit
Script done on Fri 12 Jan 2007 02:26:33 PM CET
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
participants (4)
-
Fabian Groffen -
Jan Flokstra -
Sjoerd Mullender -
Stefan Manegold