I do a test run now and see if it passes with that , why is fulvia so SLOW ??
takes about an ~hour to build with 4 threads
On Sunday 31 May 2009 02:28:28 Bill Hart wrote:
> In that case it should be sufficient to pass CFLAGS=-m64 to configure.
>
> 2009/5/31 Jason Moxham :
> > You are right
> >
>
I wonder if it is a new intel compiler or if it never worked with that
compiler. The latter seems unlikely though.
Bill.
2009/5/31 Jason Martin :
>
> GMP-4.3 also fails to compiled with icc. The intel compiler doesn't
> seem happy with the __asm__ syntax in the C files.
>
> Jason Worth Martin
>
GMP-4.3 also fails to compiled with icc. The intel compiler doesn't
seem happy with the __asm__ syntax in the C files.
Jason Worth Martin
Asst. Professor of Mathematics
http://www.math.jmu.edu/~martin
On Sat, May 30, 2009 at 8:08 PM, Bill Hart wrote:
>
> This is unfortunate. Could you make a
gcc-4.3.3 on fulvia has the same problem but cc/CC is OK
note: gcc is gcc-4.4.0 on fulvia
On Sunday 31 May 2009 02:23:08 Jason Moxham wrote:
> You are right
>
> when we select build=none we get ABI=long not ABI=64
> so that the compiler options are none rather than -m64
> this works with gcc an
In that case it should be sufficient to pass CFLAGS=-m64 to configure.
2009/5/31 Jason Moxham :
>
>
> You are right
>
> when we select build=none we get ABI=long not ABI=64
> so that the compiler options are none rather than -m64
> this works with gcc and cc on all other machines , sparc Solaris
You are right
when we select build=none we get ABI=long not ABI=64
so that the compiler options are none rather than -m64
this works with gcc and cc on all other machines , sparc Solaris included ,
darwin apple !!! (shock horror) , just not on fulvia!!!
On Sunday 31 May 2009 02:04:28 Bill
Hopefully Mariah has some idea about this. I don't see why that
wouldn't compile, except that perhaps it needs a -m64 or something
like that.
Bill.
2009/5/31 Jason Moxham :
>
> compiling
>
> int main (void) { return 0; }
>
> with
> gcc crap.cc && ./a.out
> is fine
>
> but
> g++ crap.cc && ./a.ou
compiling
int main (void) { return 0; }
with
gcc crap.cc && ./a.out
is fine
but
g++ crap.cc && ./a.out
libc.so.1: a.out:
fatal: /usr/local/gcc-4.4.0/x86_64-SunOS-core2/lib/amd64/libstdc++.so.6:
wrong ELF class: ELFCLASS64
Killed
which is what configure basically trys to do
not sure why it d
What does config.log say went wrong?
2009/5/31 Jason Moxham :
>
> ./configure --enable-cxx --build=none
> fails on fulvia with
>
> checking build system type... none-none-none
> checking host system type... none-none-none
> checking for a BSD-compatible
> install... /home/jasonmoxham/mpir/mpir/tr
./configure --enable-cxx --build=none
fails on fulvia with
checking build system type... none-none-none
checking host system type... none-none-none
checking for a BSD-compatible
install... /home/jasonmoxham/mpir/mpir/trunk/install-sh -c
checking whether build environment is sane... yes
checkin
This is unfortunate. Could you make a trac ticket for this and we'll
try to fix this for the next release.
Bill.
2009/5/31 Jason Moxham :
>
>
> On cleo we still get these errors with icc , looks like icc doesn't like our
> asm code
>
> m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_add_n -DP
On cleo we still get these errors with icc , looks like icc doesn't like our
asm code
m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_add_n -DPIC add_n.asm
>tmp-add_n.s
/bin/sh ../libtool --mode=compile --tag=CC
/home/jasonmoxham/mpir/mpir/trunk/mpn/m4-ccas --m4="m4"
icc -c99 -c -DHAVE_CO
On Saturday 30 May 2009 14:40:50 Jason Martin wrote:
> I think that icc is only available on the redhat Itanium (cleo). It
> probably won't be in the path on iras.
>
Yeah , it's not on iras , the error was on cleo , looks like a wrong path
libimf is at
/usr/local/intel-11.0.081/ia64-Linux-rhel/
I think that icc is only available on the redhat Itanium (cleo). It
probably won't be in the path on iras.
--jason
Jason Worth Martin
Asst. Professor of Mathematics
http://www.math.jmu.edu/~martin
On Sat, May 30, 2009 at 9:16 AM, Jason Moxham wrote:
>
>
> export CC=icc && configure
>
> fail
export CC=icc && configure
fails with
checking build system type... ./dummy-10941: error while loading shared
libraries: libimf.so.6: cannot open shared object file: No such file or
directory
ia64-unknown-linux-gnu
checking host system type... ia64-unknown-linux-gnu
checking for a BSD-compati
I have to go out this evening , but I'll start "try" tests for x86_64 on all
the relevant machines.
On Saturday 30 May 2009 12:09:38 Jason Moxham wrote:
> On Saturday 30 May 2009 11:55:53 Bill Hart wrote:
> > What are the outstanding issues?
>
> two were just my crappy script :)
>
> fulvia , i
On Saturday 30 May 2009 11:55:53 Bill Hart wrote:
> What are the outstanding issues?
two were just my crappy script :)
fulvia , is probably same as above , I goner look at it now
and the mark/sparc wierd issue that make check fails only sometimes.Its
probably another path/script issue , as th
What are the outstanding issues?
2009/5/30 Jason Moxham :
>
> It would of been faster to write a new itanium asm version of MPN_ZERO :)
>
> I nearly finished testing on skynet
> eno,menas,mark,cicero,sage,varro,mark2,cleo,iras,cato,fulvia
> and
> box1,2,3,modular.jmu
> I can't login to cuda1 at t
It would of been faster to write a new itanium asm version of MPN_ZERO :)
I nearly finished testing on skynet
eno,menas,mark,cicero,sage,varro,mark2,cleo,iras,cato,fulvia
and
box1,2,3,modular.jmu
I can't login to cuda1 at the moment , is it back up yet?
I've tested all the installed gcc's,cc's
Ah, this issue is discussed for GMP here:
http://gmplib.org/list-archives/gmp-bugs/2008-July/001047.html
Exactly the same thing is happening in MPIR because originally MPIR
started from the GMP codebase and no changes we have made since have
rectified this issue.
One poster to the GMP list seem
I spent hours looking for a macro for the new MPN_ZERO that gcc 4.1.2
would not miscompile on ia64 and I came to the conclusion one does not
exist. That compiler is very broken. I checked the output of the
preprocessor was correct, i.e. it wasn't misexpanding the macros. But
some kind of expressio
By the way, you original command:
./configure --enable-cxx --disable-static --enable-shared
will not work in MSYS as far as I know. MSYS does not support the
building of shared libraries for MPIR as far as I am aware. You can
only build a static library. If you want a little bit more flexibility
make clean simply removes all the files you built before.
If you do:
make
make clean
make check
it should not pass make check, as there is no library to check, since
you just cleaned it away!!
I'm checking now on my machine whether:
./configure --enable-cxx
make clean
make
make check
works.
It works just fine after reversing command
the command i type is
./configure --enable-cxx --disable-static --enable-shared
make
make check return 9 test failed
but your command works perfectly.
./configure --enable-gmpcompat
make clean
make
make check
I issue make clean after make. Is there
24 matches
Mail list logo
