On Sep 9, 2:39 am, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:

Hi,

> gmp-4.2.2.p1-fake spkg problem? (already in the 3.1.1 build install
> log):
>
> ...
> gmp-4.2.2.p1.fake/.hgignore
> Finished extraction
> ****************************************************
> Host system
> uname -a:
> Darwin susanne-webers-computer.local 8.11.1 Darwin Kernel Version
> 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/
> RELEASE_I386 i386 i386
> ****************************************************
> ****************************************************
> GCC Version
> gcc -v
> Using built-in specs.
> Target: i686-apple-darwin8
> Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure --
> disable-checking -enable-werror --prefix=/usr --mandir=/share/man --
> enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg]
> [^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-
> slibdir=/usr/lib --build=powerpc-apple-darwin8 --with-arch=nocona --
> with-tune=generic --program-prefix= --host=i686-apple-darwin8 --
> target=i686-apple-darwin8
> Thread model: posix
> gcc version 4.0.1 (Apple Computer, Inc. build 5367)
> ****************************************************
> Patching gmp-h.in (fixes OSX 10.5 issues and gcc 4.3 problems)
> Fast gcd patch:
> Moving files that are to be replaced to *.orig ...
> Copying new files across...
> Done.
> checking build system type... pentium3-apple-darwin8.11.1
> checking host system type... pentium3-apple-darwin8.11.1
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of
> Makefiles... no
> checking ABI=32
> checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer has
> sizeof(long)==4... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer  -
> mtune=pentium3... yes
> checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=pentium3  -
> march=pentium3... yes
> checking for gcc... gcc
> ...
>
> I don't have "Pentium 3" but a Core2 Duo instead, so the line
>
>    checking build system type... pentium3-apple-darwin8.11.1
>
> should be:
>
>    checking build system type... i686-apple-darwin8

Well, gmp's 4.2.1 detection of Core2 is broken and we did not consider
it worth the time to fix it before switching this months. The gmp.spkg
is fairly heavily customized and not easily upgradable. Last time we
did we ran into a boatload of trouble, so we reverted.

> instead, which is what I got when I installed gmp-4.2.1 "by hand".
> I'm just playing around with gmp 4.2.2 and 4.2.3, maybe I find out
> more.
>
> On my OS X 10.4 PPC box, the gmp situation for Sage 3.1.2.rc1 seems to
> be even worse:
>
>    checking build system type...  none-apple-darwin
>
> and the compile flags suddenly contain "-DNO_ASM".
> (The PPC box still builds and didn't run into polybori 0.5 spkg
> yet :-))
>
> Is that behaviour intended? If not, is that a new trac ticket?

No new ticket, the eMPIRe upgrade will fix that. Any gmp out there is
broken on OSX Intel when building with dynamic libraries only. The
situation on OSX/PPC is not much better.

> If the "fake" in the spkg name means that everything is prebuilt, then
> the directory .../x86/k8/ ... seems to be missing
> (there are e.g. directories .../x86/k6/... and .../x86/k7/...), but
> I've seen lines containing "mtune=k8" or something like that in
> my manual builds.

Nope, the "fake" is for upgrade purposes since that way upgrades
continue to work.

> Cheers,
> gsw

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to