-
Bug
-
Resolution: Fixed
-
P4
-
8, 11, 13, 14, 15, 16
-
b05
-
x86
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8252356 | 15.0.2 | Vladimir Kempik | P4 | Resolved | Fixed | b01 |
| JDK-8252670 | 15.0.1 | Vladimir Kempik | P4 | Resolved | Fixed | b08 |
| JDK-8248881 | 13.0.5 | Vladimir Kempik | P4 | Resolved | Fixed | b01 |
| JDK-8249819 | 11.0.9 | Vladimir Kempik | P4 | Resolved | Fixed | b01 |
For Xcode8-12 (and maybe earlier) on macos the ffi.h is located in usr/include/ffi/ffi.h path in sdk, not in system folder.
Therefore its not possible to pass additonal flags, like -I/usr/include/ffi as it will make clang to look into system's /usr/include/ffi folder (but not into sdk's usr/include/ffi) while /usr/include may (in case of Command line tools installed) or may not be present at all.
It might be reasonable to change default location for ffi.h from <ffi.h> to <ffi/ffi.h> for MacOS
ffi is needed to build Zero VM
Therefore its not possible to pass additonal flags, like -I/usr/include/ffi as it will make clang to look into system's /usr/include/ffi folder (but not into sdk's usr/include/ffi) while /usr/include may (in case of Command line tools installed) or may not be present at all.
It might be reasonable to change default location for ffi.h from <ffi.h> to <ffi/ffi.h> for MacOS
ffi is needed to build Zero VM
- backported by
-
JDK-8248881 [macos] zerovm is broken due to libffi headers location
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-