On Monday, December 3, 2012 3:55:50 PM UTC+1, Bill Hart wrote:
>
> I assume you mean divexact_1.asm. 
>
> I don't think we set -DPIC anywhere, so I think this is an autotools 
> bug. How recent is the report? It might have been fixed by the latest 
> autotools upgrade that we did. 
>
> It's quite recent, from a few days ago, been tested with MPIR 2.6.0 (and 
2.4.x with similar results).

To make things clear :
- this is with mac os 10.4 and 5 running in 32 bits mode on 64 bit intel 
hardware, so there is no PPC involved here,
- we do not set PIC in the sage spkg, nor does MPIR itself, so it seems 
that some autotools magic decide to add it by default,
- the problem is that MPIR then wants to use the corresponding asm files 
with PIC defined and these files use the @GOT construction that Apple's AS 
in this Mac OSes does not understand

Here is how we dealt with that before: delete all the problematic asm 
files, so that there is no @GOT anywhere and that did the trick.
According to Bill, and if I understood correctly, that should not be 
necessary because autotools should detect its building MPIR on Mac OS on 
intel hardware and should choose the x86/applenopic subdirectory rather 
than the files from the x86 toplevel or say from the x86/core2 subdirectory 
which contain the @GOT construction.
But that does not seem to be the case, files from other directories than 
the applenopic one are picked up here.

Not sure what to think of the PIC thing.
I guess it's quite natural that autotools tries to build PIC code by 
default if the system should be capable.
The problem here is really that it also chooses files in a wrong directory 
and in the case of PIC code, the assembly files in this directory contain 
instructions that the assembler does not understand.

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/mpir-devel/-/xkTtNdDP3J0J.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to