Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot defconfig failures
Date: Mon, 8 May 2017 14:20:23 +0200	[thread overview]
Message-ID: <20170508142023.6b95ccf7@free-electrons.com> (raw)
In-Reply-To: <df95a70f-0e89-750f-1702-25998944fc3a@c-sky.com>

Hello,

On Mon, 8 May 2017 10:33:02 +0800, ren_guo wrote:

> >   - The CSKY defconfig does not build, with "SSP support not available
> >     in this toolchain, please disable BR2_TOOLCHAIN_EXTERNAL_HAS_SSP".
> >     However, I can't reproduce locally. So I'm not sure what happening.  
> 
> Our toolchain support SSP. And I've tried the cmd from toolchain/helper.mk:419
> 
> "echo 'void main(){}' | csky-linux-gcc -fstack-protector -x c - -o hello  && echo y"
> 
> It's OK on my ubuntu 16.04.

Yes, it's OK here as well. And it seems to work fine on Gitlab CI for
many other toolchains as well. So we have something weird here.

> >     There is no hash on the toolchain tarball, but the one I downloaded
> >     locally has the exact same size as the one that was downloaded by
> >     Gitlab CI. While not an 100% guaranteed proof that it's the same
> >     toolchain, it would be unlikely to have the toolchain tarball
> >     changed in the mean time.  
> 
> Ok, I will add hash right now, thx.

Where will you add the hash? You can't add the hash in Buildroot for
custom external toolchains.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-05-08 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 12:55 [Buildroot] Buildroot defconfig failures Thomas Petazzoni
2017-05-07 13:38 ` Thomas Petazzoni
2017-05-07 19:24   ` Peter Korsgaard
2017-05-08  0:25 ` Fabio Estevam
2017-05-09 18:35   ` Fabio Estevam
2017-05-08  2:33 ` ren_guo
2017-05-08 12:20   ` Thomas Petazzoni [this message]
2017-05-08 13:43     ` ren_guo
2017-05-08 14:33       ` Arnout Vandecappelle
2017-05-09 13:49         ` ren_guo
2017-05-11 11:33         ` ren_guo
2017-05-11 11:41           ` Thomas Petazzoni
2017-05-11 12:05             ` ren_guo
2017-05-11 14:34               ` Thomas Petazzoni
2017-05-08 19:21       ` Thomas Petazzoni

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=20170508142023.6b95ccf7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox