From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Cross-compiling for aarch64 and armv6l on x86_64 does not seem to work Date: Sun, 09 Jan 2022 15:21:31 +0000 Message-ID: <4D633C0E-93F0-4B47-B02F-C8458FF985F6@ipfire.org> In-Reply-To: <3a1ce1fa-59e8-02b0-f37a-073a60b1a67a@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4576708339977352334==" List-Id: --===============4576708339977352334== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, What distribution is this? > On 9 Jan 2022, at 13:36, Peter M=C3=BCller wro= te: >=20 > Hello Michael, >=20 > thanks for your reply. >=20 >> You will need to have the =E2=80=94-target switch before the command: >>=20 >> ./make.sh =E2=80=94-target=3Daarch64 build >>=20 >> Don=E2=80=99t forget to fetch the toolchain first and you might need to in= stall a couple of packages that will emulate this architecture. An error mess= age should let you know if anything is missing. >=20 > I did so, installed some missing packages, ran "/usr/sbin/qemu-binfmt-conf.= sh", downloaded the toolchain > for aarch64, and tried to start the build. Sadly, it aborts without any (ob= vious) error message: >=20 > Packaged toolchain compilation = = = =20 > Checking for necessary space on disk = = = [ DONE ] > Building LFS = = = =20 > stage2 = = = [ FAIL ] >=20 > Jan 9 13:31:47: Building stage2 >=20 > ERROR: Building stage2 = = = [ FAIL ] > Check /home/pmu/devel/IPFire-development/ipfire-2.x/log/_build.base.log = for errors if applicable = [= FAIL ] > machine:/home/pmu/devel/IPFire-development/ipfire-2.x # cat /home/pmu/devel= /IPFire-development/ipfire-2.x/log/_build.base.log > Jan 9 13:31:47: Building stage2=20 >=20 > That's literally it. Since make.sh does not seem to support a debug/verbose= switch, and the output of > "bash -x ./make.sh --target=3Daarch64 build" does not gives any helpful inf= ormation either, I'm afraid I > have to ask for help again. Well=E2=80=A6 where does it stop? QEMU will definitely complain if something isn=E2=80=99t right. Can you see Q= EMU being executed at all? -Michael >=20 > In case it helps: >=20 > # cat /proc/sys/fs/binfmt_misc/qemu-aarch64 > enabled > interpreter /usr/bin/qemu-aarch64-binfmt > flags: P > offset 0 > magic 7f454c460201010000000000000000000200b700 > mask ffffffffffffff00fffffffffffffffffeffffff >=20 > Thanks in advance, and best regards, > Peter M=C3=BCller --===============4576708339977352334==--