From: Peter Korsgaard <peter@korsgaard.com>
To: <yann.morin@orange.com>
Cc: Anisse Astier <anisse@astier.eu>,
Christian Stewart <christian@aperture.us>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCHv2] package/go: fix installation
Date: Fri, 13 Oct 2023 16:37:13 +0200 [thread overview]
Message-ID: <871qdy612e.fsf@48ers.dk> (raw)
In-Reply-To: <87il7q5s0o.fsf@48ers.dk> (Peter Korsgaard's message of "Sun, 01 Oct 2023 16:36:23 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> <yann.morin@orange.com> writes:
>> From: "Yann E. MORIN" <yann.morin@orange.com>
>> When building for a target architecture that go does not support, the
>> isntallation fails with:
>> $ make host-go
>> [...]
>> ln -sf ../lib/go/bin/go /home/nyma7486/dev/work/5GCroCo/O/pouet/per-package/host-go/host/bin/
>> ln: failed to create symbolic link '/home/nyma7486/dev/work/5GCroCo/O/pouet/per-package/host-go/host/bin/': No such file or directory
>> Indeed, the HOST_DIR/bin is not guaranteed to exist when we install a
>> host package, so it needs to be explicitly created before we can create
>> entries in there.
>> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
>> Cc: Christian Stewart <christian@aperture.us>
>> Cc: Anisse Astier <anisse@astier.eu>
>> ---
>> Changes v1 -> v2:
>> - drop surious hunk
> Committed, thanks.
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-10-13 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 11:34 [Buildroot] [PATCHv2] package/go: fix installation yann.morin
2023-10-01 14:36 ` Peter Korsgaard
2023-10-13 14:37 ` Peter Korsgaard [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=871qdy612e.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=anisse@astier.eu \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox