Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2707] New: Can't compile linux kernel using buildroot + crosstool-ng
Date: Sat, 16 Oct 2010 19:26:07 +0000 (UTC)	[thread overview]
Message-ID: <bug-2707-163@https.bugs.busybox.net/> (raw)

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

           Summary: Can't compile linux kernel using buildroot +
                    crosstool-ng
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: phil at philpep.org
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 2605
  --> https://bugs.busybox.net/attachment.cgi?id=2605
fix missing include of kernel-headers when using crosstool-ng toolchain

linux/linux.mk need KERNEL_ARCH defined in
toolchain/kernel-headers/kernel-headers.mk included usually by toolchain
makefiles, crosstool-ng don't causing an error when we compile the linux
kernel.

Fix attached.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-10-16 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16 19:26 bugzilla at busybox.net [this message]
2010-10-17 10:00 ` [Buildroot] [Bug 2707] Can't compile linux kernel using buildroot + crosstool-ng bugzilla at busybox.net
2010-10-17 21:35 ` 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-2707-163@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox