From: James Hilliard <james.hilliard1@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Can't reproduce libnss build failure
Date: Sun, 22 May 2022 18:40:48 -0600 [thread overview]
Message-ID: <CADvTj4puraDuVBrgA_wDGAcHsMTMbioDuoveZScziQ1A2WdTqw@mail.gmail.com> (raw)
In-Reply-To: <b07a637a-9842-7852-61c1-b7ca549b0c42@benettiengineering.com>
On Sun, May 22, 2022 at 5:58 PM Giulio Benetti
<giulio.benetti@benettiengineering.com> wrote:
>
> Hi James,
>
> I'm dealing with libnss build failure with host gcc on your asahi-mini
> autobuilder, the host gcc doesn't
> like -m64 option when linking [1].
>
> I've spent many hours trying to reproduce it on various dockers and
> finally on a VM with Ubuntu 16.04
> 32 bits but in the first cases I can't have any build failure, while
> with the latter I have a different error.
It's an aarch64 host, not 32 bit x86.
>
> Can you please tell me specifically which distribution and distribution
> version you're using on asahi-mini?
> I'm on it and I'd like to fix it.
As the name implies it's asahi linux(arch based) on a mac
mini(https://asahilinux.org/).
>
> Thanks a lot
> Best regards
>
> [1]:
> http://autobuild.buildroot.net/results/dffa00b04f407715b04b1dfd8d9e5e4bc62b5ba2/
>
> ---
> Giulio Benetti
> Benetti Engineering sas
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-23 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 23:58 [Buildroot] Can't reproduce libnss build failure Giulio Benetti
2022-05-23 0:40 ` James Hilliard [this message]
2022-05-23 21:43 ` Giulio Benetti
2022-05-23 22:08 ` James Hilliard
2022-05-24 14:55 ` Giulio Benetti
2022-05-24 19:54 ` James Hilliard
2022-05-24 22:07 ` Giulio Benetti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADvTj4puraDuVBrgA_wDGAcHsMTMbioDuoveZScziQ1A2WdTqw@mail.gmail.com \
--to=james.hilliard1@gmail.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.