From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Afshin Pir <Afshin.Pir@gallagher.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Update schedule of sources.buildroot.org
Date: Fri, 25 Aug 2023 08:56:34 +0200 [thread overview]
Message-ID: <87pm3bd2zh.fsf@48ers.dk> (raw)
In-Reply-To: <20230824232658.616ff7e0@windsurf> (Thomas Petazzoni's message of "Thu, 24 Aug 2023 23:26:58 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Thu, 24 Aug 2023 23:23:53 +0200
> Peter Korsgaard <peter@korsgaard.com> wrote:
>> It is unfortunately not right away clear to me how we can do that - Make
>> source can fail for all kind of reasons.
>>
>> Any ideas?
> You could run "make busybox-source" first, to see if at least we're
> able to source a well known package that's known to work. If that fails
> (it would have failed with the missing Perl thing), we can abort and
> notify us.
Ah yes, I will have a look at implementing something like that.
I BTW noticed that host-ccache no longer builds since the bump to 4.7.4
(in 2023.05). According to
https://ccache.dev/platform-compiler-language-support.html it needs
GCC >= 8, and the machine uses GCC 4.8.5.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-25 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:36 [Buildroot] Update schedule of sources.buildroot.org Afshin Pir
2023-08-01 10:11 ` Thomas Petazzoni via buildroot
2023-08-01 21:30 ` Afshin Pir
2023-08-02 22:30 ` Afshin Pir
2023-08-03 18:51 ` Yann E. MORIN
2023-08-24 21:10 ` Peter Korsgaard
2023-08-24 21:16 ` Thomas Petazzoni via buildroot
2023-08-24 21:23 ` Peter Korsgaard
2023-08-24 21:26 ` Thomas Petazzoni via buildroot
2023-08-25 6:56 ` 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=87pm3bd2zh.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=Afshin.Pir@gallagher.com \
--cc=buildroot@buildroot.org \
--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.