https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising >users that they need to create a chroot for the {ARCH} they wish to cross build
for and also have the relevant crossbuild-essential-{ARCH} package installed?
https://wiki.debian.org/sbuild
https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising users that they need to create a chroot for the {ARCH} they wish to cross build
for and also have the relevant crossbuild-essential-{ARCH} package installed?
* A VM with Debian trixie install - standard utilities plus ssh server.
For --host=arm64 I have to generate an arm64 chroot and install crossbuild- >essential-arm64 for crossbuilds to work.
I mainly ran into issue with autopkgtest
Hi Phil,
* Phil Wyett <[email protected]> [2025-01-20 16:35]:
https://wiki.debian.org/sbuild
https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising
users that they need to create a chroot for the {ARCH} they wish to cross build
for and also have the relevant crossbuild-essential-{ARCH} package installed?
No, why?
Cross compiling means that you need that normal build arch chroot as
initial set up. An other thing is using sbuild --arch=, that uses qemu
most of the time, where you need the arch chroot.
Cheers Jochen
On Mon, 2025-01-20 at 17:53 +0100, Jochen Sprickerhof wrote:
Hi Phil,
* Phil Wyett <[email protected]> [2025-01-20 16:35]:
https://wiki.debian.org/sbuild
https://wiki.debian.org/sbuild#Cross-compiling_packages
On the sbuild wiki page in the cross compiling section should we be advising
users that they need to create a chroot for the {ARCH} they wish to cross build
for and also have the relevant crossbuild-essential-{ARCH} package installed?
No, why?
Cross compiling means that you need that normal build arch chroot as initial set up. An other thing is using sbuild --arch=, that uses qemu most of the time, where you need the arch chroot.
Cheers Jochen
Hi,
Ah... Let me describe my setup.
* A VM with Debian trixie install - standard utilities plus ssh server.
* sbuild, pbuilder, piuparts and reprotest etc. installed.
* qemu is not the install.
For --host=arm64 I have to generate an arm64 chroot and install crossbuild- essential-arm64 for crossbuilds to work.
Regards
Phil
* Phil Wyett <[email protected]> [2025-01-20 17:10]:
* A VM with Debian trixie install - standard utilities plus ssh server.
Which arch has the VM?
For --host=arm64 I have to generate an arm64 chroot and install crossbuild- essential-arm64 for crossbuilds to work.
If you want to cross build a package, i.e. your system is not arm64 and
you want to compile a package that is arm64 you need a chroot from host system arch and sbuild will take care of the rest, no need to manually install crossbuild-essential-arm64 or anything. Did you try that?
Cheers Jochen
I mainly ran into issue with autopkgtest which looked for --arch (unshare >default config) and failed unless I generated the arm64 chroot.
* Phil Wyett <[email protected]> [2025-01-20 17:10]:
* A VM with Debian trixie install - standard utilities plus ssh server.
Which arch has the VM?
For --host=arm64 I have to generate an arm64 chroot and install crossbuild- essential-arm64 for crossbuilds to work.
If you want to cross build a package, i.e. your system is not arm64 and
you want to compile a package that is arm64 you need a chroot from host system arch and sbuild will take care of the rest, no need to manually install crossbuild-essential-arm64 or anything. Did you try that?
Cheers Jochen
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 158:03:19 |
| Calls: | 12,094 |
| Calls today: | 2 |
| Files: | 15,000 |
| Messages: | 6,517,755 |