All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv1 0/4] Per-package SDK and target directories
Date: Wed, 8 Nov 2017 17:55:24 +0100	[thread overview]
Message-ID: <20171108175524.29e9a458@windsurf> (raw)
In-Reply-To: <5DBA847110A28B46BBA17BE675F0C9B2181A8D38@cnshjmbx01>

Hello,

On Tue, 7 Nov 2017 11:48:17 +0000, Chu, Zhuliang (NSB - CN/Shanghai)
wrote:

> Q3: ERROR: Could not generate syscalls.(uclibc_error.log)
> I have not solved this problem, I put the error message in the attachment

So I built a basic uClibc system, toolchain included with the following
defconfig:

BR2_arm=y
BR2_cortex_a8=y

And it built just fine.

Are you able to reproduce this problem? Does it happen every time, or
just once in a while?

Best regards,

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

  parent reply	other threads:[~2017-11-08 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5DBA847110A28B46BBA17BE675F0C9B2181A8D38@cnshjmbx01>
2017-11-07 17:13 ` [Buildroot] [RFCv1 0/4] Per-package SDK and target directories Thomas Petazzoni
2017-11-07 17:55   ` Arnout Vandecappelle
2017-11-07 19:55     ` Thomas Petazzoni
2017-11-07 20:54       ` Arnout Vandecappelle
2017-11-09  5:02     ` Chu, Zhuliang
2017-11-11 10:20       ` Arnout Vandecappelle
2017-11-09  4:32   ` Chu, Zhuliang
2017-11-11 10:37     ` Arnout Vandecappelle
2017-11-15  8:59       ` Chu, Zhuliang
2017-11-08 16:55 ` Thomas Petazzoni [this message]
2017-11-09  4:44   ` Chu, Zhuliang
2017-11-08 17:29 ` Yann E. MORIN
2017-11-08 18:35   ` Thomas De Schampheleire
2017-11-09  8:19   ` Chu, Zhuliang
2017-11-03 16:06 Thomas Petazzoni
2017-11-07 23:21 ` Arnout Vandecappelle

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=20171108175524.29e9a458@windsurf \
    --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 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.