All of lore.kernel.org
 help / color / mirror / Atom feed
From: yann.morin@orange.com
To: James Hilliard <james.hilliard1@gmail.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.org] Daily results for 2026-08-05
Date: Thu, 6 Aug 2026 07:13:37 +0200	[thread overview]
Message-ID: <anQYAedmf7UVuP63@yd-6wlzhs3> (raw)
In-Reply-To: <6a73ff1f.b251136a.3b3ec3.8c3e@mx.google.com>

James, All,

On 2026-08-06 03:27 -0000, Buildroot Notifications spake thusly:
> Autobuilder failures (excerpt from a few daily reports):
> -------------+--------------------------------+---------------------------------------------------------------------------------
>     i686     | amazon-ecr-credential-helpe... | https://autobuild.buildroot.org/results/f604fd0932c155812559a58ce7236c52ad46c020
>     i686     | amazon-ecr-credential-helpe... | https://autobuild.buildroot.org/results/9a21ed3d040ee123eb5a7611776f830e43aa19a2

It seems that, somehow, go gets confused between the host and target
architectures:

    * the host is AArch64
    * the target is i386

But the link of the *target* package fails due to relocation errors in
the arm64 go linker:

    loadelf: $WORK/b231/_pkg_.a(_x002.o): 367835: sym#69
    ("wm4.0.de6020793228b799ea3c25f2853d5666"): ignoring symbol in
section 2
    (".group") (type 0)
    /home/autobuild/autobuild/instance-4/output-1/host/lib/go/pkg/tool/linux_arm64/link:
    too many errors

James, I would need a bit of help on this one: the build fails on your
AArch64 autobuilder; and I have no AArch64 host at hand to reproduce and
debug the issue.

Regards,
Yann E. MORIN.

PS. Sorry for the triplicate message, I now see that replying to the
daily mails do not reply to the list... :-/

-- 
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2026-08-06  5:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6a73ff1f.b251136a.3b3ec3.8c3e@mx.google.com>
2026-08-06  5:13 ` yann.morin [this message]
2026-08-06  3:27 [Buildroot] [autobuild.buildroot.org] Daily results for 2026-08-05 Buildroot Notifications

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=anQYAedmf7UVuP63@yd-6wlzhs3 \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.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.