Re: Tool for generating a rootfs for foreign arch (aarch64 on x86_64, for example)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 22, 2017 at 3:03 PM, Neal Gompa <ngompa13@xxxxxxxxx> wrote:
> On Thu, Jun 22, 2017 at 9:55 AM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:
>> On Thu, Jun 22, 2017 at 9:33 AM, Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>>> On Thu, Jun 22, 2017 at 9:29 AM, John Reiser <jreiser@xxxxxxxxxxxx> wrote:
>>>> On 06/22/2017 0013Z, Neal Gompa wrote:
>>>>>
>>>>> Yes, we do have debootstrap, but it can only build Debian-based systems.
>>>>> :)
>>>>>
>>>>> I want to be able to build a Fedora based one.
>>>>
>>>>
>>>> Please be specific, and give a concrete example of what should change.
>>>>
>>>> debootstrap takes a list of .debs and builds a root filesystem that contains
>>>> them.
>>>> febootstrap takes a list of .rpms and builds a root filesystem that contains
>>>> them.
>>>> In both cases the result contains some distro-specific metadata as files:
>>>> the packaging data for maintenance of the system, which is implicit
>>>> (are not files that are contained in some input .debs or .rpms.)
>>>> In the case of Debian, the "extra" info is the apt metadata.
>>>> In the case of Fedora, the "extra" info is the dnf/yum metadata.
>>>>
>>>> Anything else?
>>>>
>>>
>>> debootstrap has the capability to utilize qemu-user-static to support
>>> constructing foreign arch rootfses. That means I can build an arm64,
>>> armhf, or ppc64el rootfs from an x86_64 host. As far as I know,
>>> febootstrap can't do this.
>>>
>>> The missing piece here is that I want to be able to construct a rootfs
>>> or an image for an architecture that *isn't* the same as my host
>>> machine.
>>
>> For what purpose?
>
> Well, it's part of a workflow to construct custom AArch64 images from
> an x86_64 PC. It's not generally feasible to do all the work on an
> SBC, and all the approaches I've found so far assume native arch for
> Fedora.
>
> In addition, it's a good gateway for being able to set up emulated
> build environments for foreign architectures in things like mock, so
> that the limitation of having real hardware can go away for people to
> test builds locally.
>
> It's a pretty huge deficiency to not have *something* for this purpose.

We have the ability to run full virtual emulated machines using
libvirt so there is *something* for this purpose and there has been
for *quite* some time and it's been documented in the wiki for as long
as it's been available:
https://fedoraproject.org/wiki/Architectures/AArch64/F25/Installation#Install_with_QEMU
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux