Ned Deily added the comment:
As of Python 3.7.0, we no longer "vendor" a copy of the libffi source for
Unix-y platforms so I believe this issue of passing the right flag values into
cpython's libffi build is no longer relevant.
--
nosy: +ned.deily
resolution: -> out of date
stage:
Martin Panter added the comment:
In the original report you mentioned a linker error caused by not using “-m64”
from CFLAGS. Perhaps would it make more sense to add LDFLAGS=“-m64”, or use
CC=“cc -m64” instead? There is also Issue 27490 and Issue 22981, both
apparently about setting the ABI wit
Dennis Clarke added the comment:
On 05/26/2016 06:01 PM, Zachary Ware wrote:
>
> Zachary Ware added the comment:
>
> Would you be interested in submitting a patch?
Right now I am trying to get a clean build of libffi outside of the
python tree and then will use the --use-system-libffi option to
Dennis Clarke added the comment:
On 05/26/2016 06:01 PM, Zachary Ware wrote:
>
> Zachary Ware added the comment:
>
> Would you be interested in submitting a patch?
Sure, of course. There are a number of problems in the Makefile(s) for a
system not using gcc and where CFLAGS and LD_foo is pretty
Zachary Ware added the comment:
Would you be interested in submitting a patch? The whole ctypes package and
the bundled libffi in particular are fairly unloved.
As a workaround, if you have libffi installed on your system, you can use the
'--with-system-ffi' flag to Python's configure script
New submission from Dennis Clarke:
While compiling from sources I see in the process :
.
.
.
creating build/temp.solaris-2.10-sun4v.64bit-3.5/libffi
checking build system type... sparc-sun-solaris2.10
checking host system type... sparc-sun-solaris2.10
checking target system type... sparc-sun-sol
