You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li><ahref="#creating-and-using-sysroots-with-qemu-deboostrap">Creating And Using Sysroots With qemu-deboostrap</a></li>
79
+
<li><ahref="#cross-compiling-with-debian-sysroots">Cross compiling with Debian sysroots</a></li>
80
80
<li><ahref="#building-for-armaarch64">Building for ARM/aarch64</a></li>
81
81
<li><ahref="#building-for-musl">Building for musl</a></li>
82
82
<li><ahref="#verifying-the-build">Verifying the Build</a></li>
@@ -628,7 +628,7 @@ <h4 id="x11-1">X11</h4>
628
628
cp: cannot stat `arm-linux-gnueabihf/libXt.so': No such file or directory</code></pre></li>
629
629
<li><p>If the X11 libraries are not properly detected by <code>configure</code>, you can point them out by <code>--with-x</code>.</p></li>
630
630
</ul>
631
-
<h3id="creating-and-using-sysroots-with-qemu-deboostrap">Creating And Using Sysroots With qemu-deboostrap</h3>
631
+
<h3id="cross-compiling-with-debian-sysroots">Cross compiling with Debian sysroots</h3>
632
632
<p>Fortunately, you can create sysroots for foreign architectures with tools provided by your OS. On Debian/Ubuntu systems, one could use <code>qemu-deboostrap</code> to create the <em>target</em> system chroot, which would have the native libraries and headers specific to that <em>target</em> system. After that, we can use the cross-compiler on the <em>build</em> system, pointing into chroot to get the build dependencies right. This allows building for foreign architectures with native compilation speed.</p>
633
633
<p>For example, cross-compiling to AArch64 from x86_64 could be done like this:</p>
634
634
<ul>
@@ -638,75 +638,133 @@ <h3 id="creating-and-using-sysroots-with-qemu-deboostrap">Creating And Using Sys
<p>Additional architectures might be supported by Debian/Ubuntu Ports.</p>
710
768
<h3id="building-for-armaarch64">Building for ARM/aarch64</h3>
711
769
<p>A common cross-compilation target is the ARM CPU. When building for ARM, it is useful to set the ABI profile. A number of pre-defined ABI profiles are available using <code>--with-abi-profile</code>: arm-vfp-sflt, arm-vfp-hflt, arm-sflt, armv5-vfp-sflt, armv6-vfp-hflt. Note that soft-float ABIs are no longer properly supported by the JDK.</p>
0 commit comments