./configure --prefix=$HOME/tmp/prefix_cleo --enable-gmpcompat make -j4
Then I ran this script:
#!/bin/bash
RUNS=100 JOBS=4
for I in `seq 1 $RUNS`; do rm -rf $HOME/tmp/prefix_cleo make -j $JOBS install > zinstall.log.$I 2>&1 CODE=$? echo Run $I of $RUNS: code $CODE if [ $CODE = 0 ]; then rm -f zinstall.log.$I fi done
which yields errors (exit status 2) on runs 8, 12, 57, 64, and 99. I've attached one of these logs. The only, common error seems to be
> We first noticed this problem when building Sage with MPIR 1.2.2 on cleo > and iras (ia64-Linux-suse). I don't know if the error is specific to > Itanium.
Leif Leonhardy has reported the same problem on a non-Itanium machine
On Friday 26 November 2010 13:00:02 Mitesh Patel wrote:
> On 11/26/2010 06:50 AM, Mitesh Patel wrote: > > We first noticed this problem when building Sage with MPIR 1.2.2 on cleo > > and iras (ia64-Linux-suse). I don't know if the error is specific to > > Itanium.
> Leif Leonhardy has reported the same problem on a non-Itanium machine
There are actually very few dependencies in MPIR , I always test with parallel builds because I'm impatient , but the one thing I almost never test for is a make install (next mpir will be tested for a make install as well) .MPIR could well have unspecified dependencies.The other possible cause is that if you are building in a directory on an NFS drive , timing issues can effect it.You could try building on a local drive , if you still get the error then its most likely bad dependencies , but if the error goes away then !maybe!
On 30 Nov., 16:18, Jason <ja...@njkfrudils.plus.com> wrote:
> There are actually very few dependencies in MPIR , I always test with parallel
> builds because I'm impatient , but the one thing I almost never test for is a
> make install (next mpir will be tested for a make install as well) .MPIR could
> well have unspecified dependencies.The other possible cause is that if you are
> building in a directory on an NFS drive , timing issues can effect it.You could
> try building on a local drive , if you still get the error then its most
> likely bad dependencies , but if the error goes away then !maybe!
The race condition in 'make install' definitely appears on local
filesystems as well.
(Just a few days ago for the first time on an old single-core Pentium
4, too, with 8 'make' jobs, Ubuntu 9.04.)
> On 30 Nov., 16:18, Jason <ja...@njkfrudils.plus.com> wrote: > > There are actually very few dependencies in MPIR , I always test with > > parallel builds because I'm impatient , but the one thing I almost never > > test for is a make install (next mpir will be tested for a make install > > as well) .MPIR could well have unspecified dependencies.The other > > possible cause is that if you are building in a directory on an NFS > > drive , timing issues can effect it.You could try building on a local > > drive , if you still get the error then its most likely bad dependencies > > , but if the error goes away then !maybe!
> The race condition in 'make install' definitely appears on local > filesystems as well.
> (Just a few days ago for the first time on an old single-core Pentium > 4, too, with 8 'make' jobs, Ubuntu 9.04.)
> On Tuesday 30 November 2010 19:40:03 leif wrote: > > On 30 Nov., 16:18, Jason <ja...@njkfrudils.plus.com> wrote: > > > There are actually very few dependencies in MPIR , I always test with > > > parallel builds because I'm impatient , but the one thing I almost > > > never test for is a make install (next mpir will be tested for a make > > > install as well) .MPIR could well have unspecified dependencies.The > > > other possible cause is that if you are building in a directory on an > > > NFS drive , timing issues can effect it.You could try building on a > > > local drive , if you still get the error then its most likely bad > > > dependencies , but if the error goes away then !maybe!
> > The race condition in 'make install' definitely appears on local > > filesystems as well.
> > (Just a few days ago for the first time on an old single-core Pentium > > 4, too, with 8 'make' jobs, Ubuntu 9.04.)
> ignoring the line ending changes because of my email
> then run autoreconf on boxen
> I can issue a mpir-2.1.4 tomorrow as I'm testing the new 2.2.0-rc3 , this is
> not problem as the change is trivial and obvious.
Thanks, this will obviously fix it.
I must admit I was rather thinking of adding an explicit prerequisite
like install-nodist_includeexecHEADERS.
Btw, at least when configuring 2.1.3 with non-empty CFLAGS (which we
do in Sage), we also have to add
* -Wl,-z,noexecstack to clear the (erroneously set) executable stack
attributes causing trouble on Fedora 14 (and other SELinux-enabled
systems),
* -Wa,-force_cpusubtype_ALL on MacOS X [10.5] PowerPC [G4], at least
with Apple's XCode GCC 4.2.1, since otherwise the assembler rejects
some code which makes use of an extended instruction set (AltiVec
extensions I think). (See http://trac.sagemath.org/sage_trac/ticket/8664#comment:47 ff. Interestingly, this apparently wasn't necessary on a MacOS X 10.4
PowerPC G5, with XCode GCC 4.0.1.)
(We also remove a lot of x86 assembly code on 32-bit MacOS X 10.4 and
10.5 Intel due to PIC issues, though I'm not sure if this is really
still necessary.)
> > ignoring the line ending changes because of my email
> > then run autoreconf on boxen
> > I can issue a mpir-2.1.4 tomorrow as I'm testing the new 2.2.0-rc3 , this > > is not problem as the change is trivial and obvious.
> Thanks, this will obviously fix it.
> I must admit I was rather thinking of adding an explicit prerequisite > like install-nodist_includeexecHEADERS.
I was going to do it the proper way , but its more code than the install-data- hook :) , I've never done a parallel install before , it wasn't worth doing for MPIR , that why it was never noticed . This probably explains why windows installation programs are so unreliable as they are GUI based and therefore multithreaded and are probably full of race conditions , so many times I have to install twice to get them to work.
> Btw, at least when configuring 2.1.3 with non-empty CFLAGS (which we > do in Sage), we also have to add
> * -Wl,-z,noexecstack to clear the (erroneously set) executable stack > attributes causing trouble on Fedora 14 (and other SELinux-enabled > systems),
This is fixed in mpir-2.2.0
> * -Wa,-force_cpusubtype_ALL on MacOS X [10.5] PowerPC [G4], at least > with Apple's XCode GCC 4.2.1, since otherwise the assembler rejects > some code which makes use of an extended instruction set (AltiVec > extensions I think). (See > http://trac.sagemath.org/sage_trac/ticket/8664#comment:47 ff. > Interestingly, this apparently wasn't necessary on a MacOS X 10.4 PowerPC > G5, with XCode GCC 4.0.1.)
I'll have to have a look at at one
> (We also remove a lot of x86 assembly code on 32-bit MacOS X 10.4 and > 10.5 Intel due to PIC issues, though I'm not sure if this is really > still necessary.)