Thorkil, myself, who else?

Hi, It looks like both Thorkil and myself see very similar problems: Mine: scons: Reading SConscript files ... Building version 0.7.0-20070712053136-custom. Checking for architecture... x86 Checking for operating system... linux2 Checking for Subversion binary... "svn" Checking for Subversion version... Found version 1.4.4. Checking for GHC binary... "ghc" Checking for GHC version 6.4.1 or later... Found version 6.6.1. Checking for C header file gmp.h... yes Checking for mpz_t integ; mpz_init (integ) in C library gmp... yes Checking for libgmp version... 4.2.1 scons: *** File "/home2/dima/repos/yhc/build/configure.py", line 109, in configure See also: http://haskell.org/pipermail/yhc/2007-July/001011.html (full message, also has debug output from scons) Thorkil's (almost identical, even on completely different architecture): scons: Reading SConscript files ... Building version 0.7.0-20070712053136-custom. Checking for architecture... (cached) ppc Checking for operating system... (cached) darwin Checking for Subversion binary... (cached) "svn" Checking for Subversion version... (cached) Found version 1.4.0. Checking for GHC binary... (cached) "ghc" Checking for GHC version 6.4.1 or later... (cached) Found version 6.6.2. Checking for C header file gmp.h... yes Checking for mpz_t integ; mpz_init (integ) in C library gmp... yes Checking for libgmp version... 4.2.1 scons: *** File "/Users/thorkilnaur/tn/YhcDarcsRepository/yhc/build/configure.py", line 109, in configure I'm suspecting gmp as the test fails exactly there. Does anyone have an older gmp (3.x) to try? PS I have gmp 3.x on an older computer. For some reason, I couldn't build Yhc completely after darcs pull (I didn't fullclean, and I am basically migrating my development away from that computer), but at least scons testing of gmp did not fail. I cannot blame on the newer gmp otherwise, as ghc works fine with it. It seems something wrong with scons. Thorkil: when were you able to build Yhc last time, and what was your gmp version then? Thanks. -- Dimitry Golubovsky Anywhere on the Web

Hello, On Friday 20 July 2007 14:56, Dimitry Golubovsky wrote:
Hi,
It looks like both Thorkil and myself see very similar problems:
Mine:
scons: Reading SConscript files ... Building version 0.7.0-20070712053136-custom. Checking for architecture... x86 Checking for operating system... linux2 Checking for Subversion binary... "svn" Checking for Subversion version... Found version 1.4.4. Checking for GHC binary... "ghc" Checking for GHC version 6.4.1 or later... Found version 6.6.1. Checking for C header file gmp.h... yes Checking for mpz_t integ; mpz_init (integ) in C library gmp... yes Checking for libgmp version... 4.2.1
scons: *** File "/home2/dima/repos/yhc/build/configure.py", line 109, in configure
See also: http://haskell.org/pipermail/yhc/2007-July/001011.html (full message, also has debug output from scons)
Thorkil's (almost identical, even on completely different architecture):
scons: Reading SConscript files ... Building version 0.7.0-20070712053136-custom. Checking for architecture... (cached) ppc Checking for operating system... (cached) darwin Checking for Subversion binary... (cached) "svn" Checking for Subversion version... (cached) Found version 1.4.0. Checking for GHC binary... (cached) "ghc" Checking for GHC version 6.4.1 or later... (cached) Found version 6.6.2. Checking for C header file gmp.h... yes Checking for mpz_t integ; mpz_init (integ) in C library gmp... yes Checking for libgmp version... 4.2.1
scons: *** File "/Users/thorkilnaur/tn/YhcDarcsRepository/yhc/build/configure.py", line 109, in configure
I'm suspecting gmp as the test fails exactly there. Does anyone have an older gmp (3.x) to try?
PS I have gmp 3.x on an older computer. For some reason, I couldn't build Yhc completely after darcs pull (I didn't fullclean, and I am basically migrating my development away from that computer), but at least scons testing of gmp did not fail.
I cannot blame on the newer gmp otherwise, as ghc works fine with it. It seems something wrong with scons.
Thorkil: when were you able to build Yhc last time, and what was your gmp version then?
There are two Yhc instances on my machine: The first is used by the buildbot. Last build was http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106 "Building version 0.7.0-20070712053136." and that build was successful. The second instance is the one I use when I want to play with Yhc. It is several months ago that I upgraded it last, so that is what I was in the process of doing when I ran into this error. The gmp version at that time was 4.2.1, as now. In fact, I don't think I ever had another gmp on this machine. So it seems that this is unlikely to be the problem.
Thanks.
-- Dimitry Golubovsky
Anywhere on the Web
Thanks and best regards Thorkil

Hi,
On 7/20/07, Thorkil Naur
There are two Yhc instances on my machine: The first is used by the buildbot. Last build was http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106 "Building version 0.7.0-20070712053136." and that build was successful.
The two last patches (incl xxx53136) were mine, but they changed files that are outside the building tree. And there were no patches at all since then. I ran into the same error when I set up a clean virtual machine with ArchLinux, and downloaded the whole Yhc repo, on Jul 14. Looking at the inventory file, I see this: [Update scons build yhc, scons update and scons push to work with the new Yhc compiler directory Neil Mitchell**20070626130702] [Split out the gmp_configure bit, and only do it if building Yhi Neil Mitchell**20070626143401] [Add a little bit more trickery to try and get GMP detection working again Neil Mitchell**20070626144901] these are 3 last patches where GMP and scons are mentioned. Neil: did you encounter anything like this (scons fails on line 109 of configure.py) if building from scratch, before or after these patches? When enabling more debug messages in scons output, something related to "NoneType object is not callable" or similar, I'm guessing this is kind of null pointer exception in Python? -- Dimitry Golubovsky Anywhere on the Web

Hi,
On 7/20/07, Thorkil Naur
There are two Yhc instances on my machine: The first is used by the buildbot. Last build was http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106 "Building version 0.7.0-20070712053136." and that build was successful.
Are buildbot builds incremental, or they are done from scratch every time? Incremental builds to my knowledge do not recheck things like gmp as this information is cached by scons. -- Dimitry Golubovsky Anywhere on the Web

Hello, On Friday 20 July 2007 16:19, Dimitry Golubovsky wrote:
Hi,
On 7/20/07, Thorkil Naur
wrote: There are two Yhc instances on my machine: The first is used by the buildbot. Last build was http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106 "Building version 0.7.0-20070712053136." and that build was successful.
Are buildbot builds incremental, or they are done from scratch every time? Incremental builds to my knowledge do not recheck things like gmp as this information is cached by scons.
From http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106/step-shell/0, it appears that the buildbot builds are incremental. Although I don't see anything in that particular configure log that deals with gmp, this is very likely the explanation why buildbot builds can continue to work, even if fresh builds fail. Maybe I should go and erase my buildbot slave's build directory, someone might notice ...
-- Dimitry Golubovsky
Anywhere on the Web
Thanks and best regards Thorkil

Thorkil,
On 7/20/07, Thorkil Naur
From http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106/step-shell/0, it appears that the buildbot builds are incremental. Although I don't see
Maybe I should go and erase my buildbot slave's build directory, someone might notice ...
Perhaps you might try: this must force the fresh build. At least I'd narrow this down to scons itself (tonight I'll try to see what was done around GMP tests). Thanks. -- Dimitry Golubovsky Anywhere on the Web

Hello, On Friday 20 July 2007 16:50, Dimitry Golubovsky wrote:
Thorkil,
On 7/20/07, Thorkil Naur
wrote: From http://www.indiegigs.co.uk:8010/macosx_ppc_3/builds/106/step-shell/0, it appears that the buildbot builds are incremental. Although I don't see
Maybe I should go and erase my buildbot slave's build directory, someone might notice ...
Perhaps you might try: this must force the fresh build.
I removed the build tree and forced a build, but somehow, scons wriggled out of trouble: The configure log output still says something about cached stuff and the build has now proceeded past configuring. I have no idea where this cache is located.
At least I'd narrow this down to scons itself (tonight I'll try to see what was done around GMP tests).
Thanks.
-- Dimitry Golubovsky
Anywhere on the Web
Best regards Thorkil
participants (2)
-
Dimitry Golubovsky
-
Thorkil Naur