| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The stdcall issue on Windows seems to be fixed.
To update an existing working directory use:
git submodule update --init --remote
|
| |
|
|
|
|
|
|
| |
This temporary switches to a forked libffi, until the fixing PR is merged:
https://github.com/libffi/libffi/pull/465
Use the following command to update the submodule:
git submodule update --init --remote
|
|
|
* prepare for libffi submodule
remove libffi from tree
* return libffi
This time as a submodule.
* update dependency
* add autogen.sh to makefile stubs
libffi uses autoconf; a fresh checkout does not have a configure script
* don't build docs
* Bump libffi to current HEAD
* Fix HAVE_FFI_PREP_CIF_VAR define
If vendored library used `have_func('ffi_prep_cif_var')` call always
returns `false`. Because of that `ffi_prep_cif` was used which caused
many failures related to double/float on PPC64LE platform.
Fixes #413
* Mention submodule in README
* Fix gem install command in README
* Bump rake-compiler-dock
Use latest version with Ubuntu 17.04 base image
* Fix rake gem:windows command
configure.ac:187: error: possibly undefined macro: LT_SYS_SYMBOL_USCORE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
* Fix building 2.1/2.2 on macOS
* Unmask 2.3 on macOS
|
