The fat build might not work on 64 bit machines either. It looks like some
new CPUs have been added, but not to the fat binary system.

That might just be a bug in need of fixing before 2.7.0 becomes beta and
release.

I'm vaguely intending on working on MPIR-2.7.0 next month some time. But
there are so many things on my todo list, it is hard to predict if I will
actually manage it or not.

Bill.

On 18 February 2015 at 21:47, Volker Braun <vbraun.n...@gmail.com> wrote:

> Well as one data point, Sage did have i386 binaries before the update
> to mpir-2.7.0-alpha12.tar.bz2
>
> On Wednesday, February 18, 2015 at 9:19:50 PM UTC+1, Bill Hart wrote:
>>
>> Not a known issue, but also not of concern. Fat binary builds don't need
>> to work on everyone's machines, just on some machine that someone producing
>> binaries has access too. The fat build process is pretty fragile, and not
>> terribly well maintained.
>>
>> Bill.
>>
>> On 18 February 2015 at 21:17, Volker Braun <vbrau...@gmail.com> wrote:
>>
>>> Is this a known issue? See http://trac.sagemath.org/ticket/17806
>>>
>>> Configuring MPIR with the following options:
>>>     --prefix="/home/buildslave-sage/slave/sage_git/build/local"
>>> --libdir="/home/buildslave-sage/slave/sage_git/build/local/lib"
>>> --enable-fat --enable-cxx --enable-static --enable-gmpcompat
>>> --enable-shared
>>>
>>> ...
>>>
>>> In file included from fat.c:123:0:
>>> ../cpuid.c: In function '__gmpn_cpu':
>>> ../cpuid.c:96:47: error: 'CPUSETUP_ivybridge' undeclared (first use in
>>> this function)
>>>  #define CPUIS(x) do{TRACE(printf("  "#x"\n"));CPUSETUP_##x;}while(0)
>>>                                                ^
>>> ../cpuid.c:174:24: note: in expansion of macro 'CPUIS'
>>>       if (model == 58){ CPUIS(ivybridge);break;}
>>>                         ^
>>> ../cpuid.c:96:47: note: each undeclared identifier is reported only once
>>> for each function it appears in
>>>  #define CPUIS(x) do{TRACE(printf("  "#x"\n"));CPUSETUP_##x;}while(0)
>>>                                                ^
>>> ../cpuid.c:174:24: note: in expansion of macro 'CPUIS'
>>>       if (model == 58){ CPUIS(ivybridge);break;}
>>>                         ^
>>> ../cpuid.c:96:47: error: 'CPUSETUP_haswell' undeclared (first use in
>>> this function)
>>>  #define CPUIS(x) do{TRACE(printf("  "#x"\n"));CPUSETUP_##x;}while(0)
>>>                                                ^
>>> ../cpuid.c:175:22: note: in expansion of macro 'CPUIS'
>>>     if (model == 60){ CPUIS(haswell);break;}
>>>                       ^
>>> ../cpuid.c:96:47: error: 'CPUSETUP_piledriver' undeclared (first use in
>>> this function)
>>>  #define CPUIS(x) do{TRACE(printf("  "#x"\n"));CPUSETUP_##x;}while(0)
>>>                                                ^
>>> ../cpuid.c:230:24: note: in expansion of macro 'CPUIS'
>>>       if (model == 2) { CPUIS(piledriver); break; }
>>>                         ^
>>> make[6]: *** [fat.lo] Error 1
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "mpir-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mpir-devel+...@googlegroups.com.
>>> To post to this group, send email to mpir-...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/mpir-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "mpir-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mpir-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to mpir-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/mpir-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mpir-devel+unsubscr...@googlegroups.com.
To post to this group, send email to mpir-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to