From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Perale <thomas.perale@essensium.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas Perale <thomas.perale@mind.be>,
Anisse Astier <anisse@astier.eu>,
Christian Stewart <christian@aperture.us>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] Add go-bin virtual package to go providers
Date: Sun, 15 Sep 2024 16:18:26 +0200 [thread overview]
Message-ID: <ZubssqRnLr2bP9nd@landeda> (raw)
In-Reply-To: <20240914152323.2630539-1-thomas.perale@mind.be>
Thomas, All,
On 2024-09-14 17:23 +0200, Thomas Perale via buildroot spake thusly:
> Previous patch set adding 'go-bin' failed the tests in newer go version
> because of illegal instructions.
>
> This patch set fix the cross-compilation issue coming from the 'go-bin'
> this was solved by specifically mentionning the GOARM version in
> environment variable when building a go package for the target
> (`HOST_GO_TARGET_ENV`).
I applied the series with a few changes, see the commits.
I also added three preparatory commits;
559bb33ae7 support/testing: do not use s.b.o
e9b0893a8e package/go/go-src: share download directory with go
8931e9f534 support/testing: switch go-src to use flannel
Thanks a lot for this work! 👍
Regards,
Yann E. MORIN.
> Thomas Perale (2):
> package/go/go-bin: new host-go provider
> support/testing: add tests for Go providers
>
> package/go/Config.in.host | 22 ++++++++++++++++------
> package/go/go-bin/Config.in.host | 13 +++++++++++++
> package/go/go-bin/go-bin.hash | 8 ++++++++
> package/go/go-bin/go-bin.mk | 20 ++++++++++++++++++++
> package/go/go.mk | 2 ++
> support/testing/tests/package/test_go.py | 14 ++++++++++++++
> 6 files changed, 73 insertions(+), 6 deletions(-)
> create mode 100644 package/go/go-bin/Config.in.host
> create mode 100644 package/go/go-bin/go-bin.hash
> create mode 100644 package/go/go-bin/go-bin.mk
>
> --
> 2.46.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-15 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 15:23 [Buildroot] [PATCH 0/2] Add go-bin virtual package to go providers Thomas Perale via buildroot
2024-09-14 15:23 ` [Buildroot] [PATCH 1/2] package/go/go-bin: new host-go provider Thomas Perale via buildroot
2024-09-15 14:14 ` Yann E. MORIN
2024-09-14 15:23 ` [Buildroot] [PATCH 2/2] support/testing: add tests for Go providers Thomas Perale via buildroot
2024-09-15 14:16 ` Yann E. MORIN
2024-09-15 14:18 ` Yann E. MORIN [this message]
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=ZubssqRnLr2bP9nd@landeda \
--to=yann.morin.1998@free.fr \
--cc=anisse@astier.eu \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.perale@essensium.com \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.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.