All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-12-16
Date: Mon, 17 Dec 2018 09:06:46 +0100	[thread overview]
Message-ID: <875zvs4lwp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181217070031.7A1922072F@mail.bootlin.com> (Thomas Petazzoni's message of "Mon, 17 Dec 2018 08:00:31 +0100 (CET)")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 >      aarch64 |               swupdate-2018.11 | NOK | http://autobuild.buildroot.net/results/e302d0edb59ff7617b5f2d21f06eb65ae04981fe |     
 >          arm |               swupdate-2018.11 | NOK | http://autobuild.buildroot.net/results/dbb69acadc20b4bb559311348eca276c1e6343f7 |     

/bin/sh: /home/naourr/work/instance-0/output/host/bin/aarch64-linux-gnu-cc: No such file or directory

swupdate uses $CROSS-cc and not $CROSS-gcc, which not all external
toolchain have. I think it makes sense to add a cc -> gcc symlink for
external toolchains we download if not present. We cannot really do it
for pre-installed external toolchains as we might not have write access
to them.

I'll send a patch.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-12-17  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-12-16 Thomas Petazzoni
2018-12-17  8:06 ` Peter Korsgaard [this message]
2018-12-17  8:08   ` Thomas Petazzoni
2018-12-17  8:25     ` Peter Korsgaard
2018-12-17 23:43       ` Arnout Vandecappelle
2018-12-18  7:50         ` Thomas Petazzoni
2018-12-18  8:27         ` Peter Korsgaard

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=875zvs4lwp.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.