1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.MENTOR

  • Testing package on mipsel and armel

    From Aaron Boxer@21:1/5 to All on Wed Sep 14 15:50:01 2022
    Hello,
    I currently have failed builds on mipsel and armel archs.
    For these systems, it appears that I need to link explicitly
    to libatomic. I've added the link flag, but the failures persist.

    Any suggestions on setting up VMs for these architectures so
    I can directly debug my builds ?

    Thanks,
    Aaron

    <div dir="ltr">Hello,<div>I currently have failed builds on mipsel and armel archs.</div><div>For these systems, it appears that I need to link explicitly</div><div>to libatomic. I&#39;ve added the link flag, but the failures persist.</div><div><br></div>
    <div>Any suggestions on setting up VMs for these architectures so</div><div>I can directly debug my builds ?</div><div><br></div><div>Thanks,</div><div>Aaron</div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bo YU@21:1/5 to Aaron Boxer on Wed Sep 14 16:40:01 2022
    Hi,
    On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:
    Hello,
    I currently have failed builds on mipsel and armel archs.
    For these systems, it appears that I need to link explicitly
    to libatomic. I've added the link flag, but the failures persist.

    Any suggestions on setting up VMs for these architectures so
    I can directly debug my builds ?

    I just setup they some day ago on x86 pc:
    (maybe it need binfmt-support or qemu-binfmt)

    ```
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=mipsel \
    --make-sbuild-tarball=/srv/sid-mipsel-sbuild.tgz \
    sid /tmp/chroots/sid-mipsel-sbuild/ \
    http://ftp.debian.org/debian/

    # and
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=armel \
    --make-sbuild-tarball=/srv/sid-armel-sbuild.tgz \
    sid /tmp/chroots/sid-armel-sbuild/ \
    http://ftp.debian.org/debian/

    ```
    They will setup their arch chroot then can use sbuild to build the
    package.

    `sbuild --arch=mipsel -c sid-mipsel-sbuild `


    Thanks,
    Aaron

    --
    Regards,
    --
    Bo YU


    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEIcmhjYVTlmab0tjp+RVP3hQ+S68FAmMh5ewACgkQ+RVP3hQ+ S69cTg/7B4wecr3y4U3OLJkpF5WHGUVD6vWqirUqqLXViezEFElYXPVNvXW/x+uC 8jmyDFySxXHFbhh2iZv60AN/ptdbkF2maJV8BKA9z7ADPZ+bYL4dH1cPsA+pj+EK km9lEWm/TR+sKq+H/nvFLBS4OlLlA78tqLVUVDTlo698jJF9RSBwA5MYlmOy2TRT DE03mDruEcuxdZ0In+w8vP5WiWmh9SIN53hSmtiw59e689Z5tPQVutpoCzN7g65w FkiFMdvOIafact7DZnolKCaH6rgXDOkGA3W4Nc/M9UhX/cqbmx1F4WnQOcpf9kmi x/pVokGe1pIoBZPy0mpkFiuPLxTUFbcQSW2YPhQU2fHwbn0i28fSQWBkB5GHFBIc sT05xiXCGnA1Kr13Bd0xBvm0wp0DHafdOit2lQqKVkN50nwVZuNWCCZmfQeg/vwA bw1HWzX3HekdrCFpSiFRuhipvnZQiUy0qbZFUwg4makIYTrfr3AaLiMRsWCr2YIJ orurdg+HfB6G/h0Q2WhPXd5e2JBToHQB/XK0K4H6ZXeAZJekl/WS5QPwVwsWtH0P M8EqZ8Zpt6qFiNO3ub5juUhWxpeVIpJvPrb22yMkTod35DWVZ6wK1kew68mb6MgW xK30JosYKpUKntZE3apuc/KjIBV9j7V9v+WIaFS3iYcI4kU1S5I=
    =JisE
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matthew Fernandez@21:1/5 to Bo YU on Wed Sep 14 17:00:01 2022
    On 9/14/22 07:32, Bo YU wrote:
    Hi,
    On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:
    Hello,
    I currently have failed builds on mipsel and armel archs.
    For these systems, it appears that I need to link explicitly
    to libatomic. I've added the link flag, but the failures persist.

    Any suggestions on setting up VMs for these architectures so
    I can directly debug my builds ?

    I just setup they some day ago on x86 pc:
    (maybe it need binfmt-support or qemu-binfmt)

    ```
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=mipsel \
            --make-sbuild-tarball=/srv/sid-mipsel-sbuild.tgz \
            sid /tmp/chroots/sid-mipsel-sbuild/ \
            http://ftp.debian.org/debian/

    # and sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=armel \
            --make-sbuild-tarball=/srv/sid-armel-sbuild.tgz \
            sid /tmp/chroots/sid-armel-sbuild/ \
            http://ftp.debian.org/debian/

    ```
    They will setup their arch chroot then can use sbuild to build the
    package.

    `sbuild --arch=mipsel -c sid-mipsel-sbuild `

    I have a similar issue where a libatomic-related bug was filed against a package I maintain¹ but buildd results indicate the relevant platforms
    (arm64 and armel in my case) are passing. Are there different test
    environments in play on the servers and/or does this affect whether
    libatomic is linked in automatically?

    (Apologies for derailing the thread if my problem is unrelated to Aaron’s)

    ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018205

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aaron Boxer@21:1/5 to [email protected] on Wed Sep 14 22:50:01 2022
    On Wed, Sep 14, 2022 at 10:32 AM Bo YU <[email protected]> wrote:

    Hi,
    On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:
    Hello,
    I currently have failed builds on mipsel and armel archs.
    For these systems, it appears that I need to link explicitly
    to libatomic. I've added the link flag, but the failures persist.

    Any suggestions on setting up VMs for these architectures so
    I can directly debug my builds ?

    I just setup they some day ago on x86 pc:
    (maybe it need binfmt-support or qemu-binfmt)

    ```
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=mipsel \
    --make-sbuild-tarball=/srv/sid-mipsel-sbuild.tgz \
    sid /tmp/chroots/sid-mipsel-sbuild/ \
    http://ftp.debian.org/debian/

    # and
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=armel \
    --make-sbuild-tarball=/srv/sid-armel-sbuild.tgz \
    sid /tmp/chroots/sid-armel-sbuild/ \
    http://ftp.debian.org/debian/

    ```
    They will setup their arch chroot then can use sbuild to build the
    package.

    `sbuild --arch=mipsel -c sid-mipsel-sbuild `



    Thanks, I wasn't able to get that working, but I did find away following
    these instructions


    https://www.antixforum.com/forums/topic/use-sbuild-to-automate-deb-package-building/

    This helped me create the chroot for mipsel, run the chroot, and build the package.






    Thanks,
    Aaron

    --
    Regards,
    --
    Bo YU



    <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 14, 2022 at 10:32 AM Bo YU &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class="gmail_
    quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
    On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:<br>
    &gt;Hello,<br>
    &gt;I currently have failed builds on mipsel and armel archs.<br>
    &gt;For these systems, it appears that I need to link explicitly<br>
    &gt;to libatomic. I&#39;ve added the link flag, but the failures persist.<br> &gt;<br>
    &gt;Any suggestions on setting up VMs for these architectures so<br>
    &gt;I can directly debug my builds ?<br>

    I just setup they some day ago on x86 pc:<br>
    (maybe it need binfmt-support or qemu-binfmt)<br>

    ```<br>
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=mipsel \<br>
             --make-sbuild-tarball=/srv/sid-mipsel-sbuild.tgz \<br>
             sid /tmp/chroots/sid-mipsel-sbuild/ \<br>
             <a href="http://ftp.debian.org/debian/" rel="noreferrer" target="_blank">http://ftp.debian.org/debian/</a><br>

    # and <br>
    sudo sbuild-createchroot --debootstrap=mmdebstrap --arch=armel \<br>
             --make-sbuild-tarball=/srv/sid-armel-sbuild.tgz \<br>
             sid /tmp/chroots/sid-armel-sbuild/ \<br>
             <a href="http://ftp.debian.org/debian/" rel="noreferrer" target="_blank">http://ftp.debian.org/debian/</a><br>

    ```<br>
    They will setup their arch chroot then can use sbuild to build the<br> package.<br>

    `sbuild --arch=mipsel -c sid-mipsel-sbuild `<br></blockquote><div><br></div><div><br></div><div>Thanks, I wasn&#39;t able to get that working, but I did find away following these instructions</div><div><br></div><div><br></div><div><a href="https://www.
    antixforum.com/forums/topic/use-sbuild-to-automate-deb-package-building/">https://www.antixforum.com/forums/topic/use-sbuild-to-automate-deb-package-building/</a><br></div><div><br></div><div>This helped me create the chroot for mipsel, run the chroot,
    and build the package.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

    &gt;<br>
    &gt;Thanks,<br>
    &gt;Aaron<br>

    -- <br>
    Regards,<br>
    --<br>
       Bo YU<br>

    </blockquote></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)