diff options
| author | Xi Ruoyao <xry111@mengyan1223.wang> | 2022-03-26 23:21:06 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@mengyan1223.wang> | 2022-03-26 23:25:36 +0800 |
| commit | ab7af9e6f0b84495f5f8098da810727e51837c1e (patch) | |
| tree | 9ea22a39eee495228a74f163432e92f22c7a1893 /chapter08/libffi.xml | |
| parent | 827cc05c379bb251da3993f1ba316758ffdff87d (diff) | |
libffi: reword the note about "building for another system"
Telling the user to override CFLAGS and CXXFLAGS may cause two problems:
1. We've added --with-gcc-arch=native, so the configure script will add
"-march=native" into CFLAGS. Then we've not really verified which
-march= value is the last one in the GCC command line and being really
used.
2. User may just export CFLAGS="-march=x86_64", without "-O2". This
will produce unoptimized binaries.
Diffstat (limited to 'chapter08/libffi.xml')
| -rw-r--r-- | chapter08/libffi.xml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/chapter08/libffi.xml b/chapter08/libffi.xml index d71f8d2e6..4f778961d 100644 --- a/chapter08/libffi.xml +++ b/chapter08/libffi.xml @@ -44,8 +44,10 @@ <note> <para>Similar to GMP, libffi builds with optimizations specific - to the processor in use. If building for another system, export - CFLAGS and CXXFLAGS to specify a generic build for your architecture. + to the processor in use. If building for another system, change the + value of the <parameter>--with-gcc-arch=</parameter> parameter in the + following command to an architecture name fully implemented by the + CPU on that system. If this is not done, all applications that link to libffi will trigger Illegal Operation Errors.</para> </note> |