Re: [Monetdb-developers] IMPORTANT: imminent change to repositories
On Tue, Jan 02, 2007 at 11:51:30AM +0100, Arjen P. de Vries wrote:
Arjen,
to me, this looks pretty much like outdated buildtools...
take a new virgin shell remove all your (new) build directories (and your prefix(es), if easily possible) make sure that your buildtools are cvs-updated (and not locally patched) only then(!) source conf/conf.bash for buildtools then ./de-bootstrap && boostrap && configure && make install buildtools then cvs update MonetDB (and remove/undo local patches) then source conf/conf.bash for MonetDB then ./de-bootstrap && boostrap && configure && make install MonetDB and proceed analogously with clients, MonetDB4, etc.
Stefan
So it must be historic MonetDB stuff; do you think the following is also related to a previous 4.15 build?
Building clients, I get the error src/odbc/Makefile.am:13: NATIVE_WIN32 does not appear in AM_CONDITIONAL in bootstrap.
I fixed it by editing this Makefile.am, and redoing the last Mbootstrap commands (automake and autoconf).
Again, make fails on include $(top_srcdir)/*.mk
now a symlink does not help.
Cheers,
Arjen
On 01/01/07, Arjen P. de Vries arjen@acm.org wrote:
MonetDB does not depend on anything else.
In directory MonetDB, I had to link conf/rules.mk to rules.mk for making to start working; later more,
Arjen
--
CWI, room C1.16 Centre for Mathematics and Computer Science Kruislaan 413 Email: Arjen.de.Vries@cwi.nl 1098 SJ Amsterdam tel: +31-(0)20-5924306 The Netherlands fax: +31-(0)20-5924312 ===================== http://www.cwi.nl/~arjen/ ====================
to me, this looks pretty much like outdated buildtools...
still surprising... as I did cvs update and even the cvs diff to check. The steps below have all already been done.
The only thing I could imagine is that python finds some old module or something.
I'll struggle some more...
take a new virgin shell remove all your (new) build directories (and your prefix(es), if easily possible) make sure that your buildtools are cvs-updated (and not locally patched) only then(!) source conf/conf.bash for buildtools then ./de-bootstrap && boostrap && configure && make install buildtools then cvs update MonetDB (and remove/undo local patches) then source conf/conf.bash for MonetDB then ./de-bootstrap && boostrap && configure && make install MonetDB and proceed analogously with clients, MonetDB4, etc.
Stefan
So it must be historic MonetDB stuff; do you think the following is also related to a previous 4.15 build?
Building clients, I get the error src/odbc/Makefile.am:13: NATIVE_WIN32 does not appear in AM_CONDITIONAL in bootstrap.
I fixed it by editing this Makefile.am, and redoing the last Mbootstrap commands (automake and autoconf).
Again, make fails on include $(top_srcdir)/*.mk
now a symlink does not help.
Cheers,
Arjen
On 01/01/07, Arjen P. de Vries arjen@acm.org wrote:
MonetDB does not depend on anything else.
In directory MonetDB, I had to link conf/rules.mk to rules.mk for making to start working; later more,
Arjen
--
CWI, room C1.16 Centre for Mathematics and Computer Science Kruislaan 413 Email: Arjen.de.Vries@cwi.nl 1098 SJ Amsterdam tel: +31-(0)20-5924306 The Netherlands fax: +31-(0)20-5924312 ===================== http://www.cwi.nl/~arjen/ ====================
-- | 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 02-01-2007 12:03:25 +0100, Arjen P. de Vries wrote:
to me, this looks pretty much like outdated buildtools...
still surprising... as I did cvs update and even the cvs diff to check. The steps below have all already been done.
Check that you're not on a tag or something
The only thing I could imagine is that python finds some old module or something.
Clean/move your target (MONETDB_PREFIX), that reduces the possible confusion chance.
Hi,
I'm having trouble compiling MonetDB on the cluster (I'm trying core-1). I follow the instructions Stefan gave to Arjen last week:
Stefan Manegold wrote:
take a new virgin shell remove all your (new) build directories (and your prefix(es), if easily possible) make sure that your buildtools are cvs-updated (and not locally patched)
I completely removed all src, build and prefix directories and did a fresh checkout from cvs.
only then(!) source conf/conf.bash for buildtools then ./de-bootstrap && boostrap && configure && make install buildtools
bootstrap and configure are OK, but make gives a warning:
make: warning: Clock skew detected. Your build may be incomplete.
If I ignore the warning and continue installing MonetDB (also from clean directories and new checked out sources), It stops during configure with the following error message:
checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock
Suggestions?
Thijs
On 2007-01-11 12:54, Thijs Westerveld wrote:
Hi,
I'm having trouble compiling MonetDB on the cluster (I'm trying core-1). I follow the instructions Stefan gave to Arjen last week:
Stefan Manegold wrote:
take a new virgin shell remove all your (new) build directories (and your prefix(es), if easily possible) make sure that your buildtools are cvs-updated (and not locally patched)
I completely removed all src, build and prefix directories and did a fresh checkout from cvs.
only then(!) source conf/conf.bash for buildtools then ./de-bootstrap && boostrap && configure && make install buildtools
bootstrap and configure are OK, but make gives a warning:
make: warning: Clock skew detected. Your build may be incomplete.
If I ignore the warning and continue installing MonetDB (also from clean directories and new checked out sources), It stops during configure with the following error message:
checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock
Suggestions?
Get whoever is responsible to fix the clock on core-1. It's 3 minutes off!
On 11-01-2007 12:54:43 +0100, Thijs Westerveld wrote:
checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock
Suggestions?
Go to Matthijs. Your system looks b0rkened.
On 11-01-2007 13:11:40 +0100, Fabian Groffen wrote:
On 11-01-2007 12:54:43 +0100, Thijs Westerveld wrote:
checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock
Suggestions?
Go to Matthijs. Your system looks b0rkened.
I think the problem is related to you using NFS based storage. The clocks of the machine you're on and the NFS storage host are different. All machines should run ntpd to avoid this problem.
(sorry for the spam)
Fabian Groffen wrote:
I think the problem is related to you using NFS based storage. The clocks of the machine you're on and the NFS storage host are different. All machines should run ntpd to avoid this problem.
That's it. My BUILDDIRs for buildtools and MonetDB were on different filesystems. Now everything is in the same place and the problems are gone (without fixing the clock).
Thanks, Thijs
participants (5)
-
Arjen P. de Vries -
Fabian Groffen -
Sjoerd Mullender -
Stefan Manegold -
Thijs Westerveld