All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11036] C compiler cannot create executables
Date: Wed, 23 May 2018 17:03:30 +0000	[thread overview]
Message-ID: <bug-11036-163-vqZ7pyToYZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11036-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11036

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
OK. Could you try to provide a defconfig that exhibits the problem but does not
use your own private BR2_EXTERNAL tree, so that we could try to reproduce the
issue ?

Since it's the toolchain that is failing to build, normally only those options
would be needed to reproduce the problem:

BR2_arm=y
BR2_cortex_a8=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_9=y

the other options should not affect the toolchain build, except if your patches
on gcc/binutils in $(BR2_EXTERNAL_BERNARDO_PATH)/board/bernardo/patches.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-05-23 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 14:44 [Buildroot] [Bug 11036] New: C compiler cannot create executables bugzilla at busybox.net
2018-05-23 14:58 ` [Buildroot] [Bug 11036] " bugzilla at busybox.net
2018-05-23 15:03 ` bugzilla at busybox.net
2018-05-23 17:03 ` bugzilla at busybox.net [this message]
2018-05-23 21:29 ` bugzilla at busybox.net
2018-05-24  6:23 ` bugzilla at busybox.net

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=bug-11036-163-vqZ7pyToYZ@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.