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 2869] New: Do not erase source and build directories from the linux kernel build.
Date: Tue, 30 Nov 2010 19:53:02 +0000 (UTC)	[thread overview]
Message-ID: <bug-2869-163@https.bugs.busybox.net/> (raw)

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

           Summary: Do not erase source and build directories from the
                    linux kernel build.
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mroberto at cpti.cetuc.puc-rio.br
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 2743
  --> https://bugs.busybox.net/attachment.cgi?id=2743
Patch to keep the "source" and "build" directories in the linux tree.

When buiding and installing a package that compiles an out-of-the-tree
kernel module, it is necessary to have the "source" and "build"
directories on the linux kernel tree. This patch avoids the deletion
of these directories in linux.mk.

-- 
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-11-30 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 19:53 bugzilla at busybox.net [this message]
2010-12-22  9:18 ` [Buildroot] [Bug 2869] Do not erase source and build directories from the linux kernel build bugzilla at busybox.net
2011-01-07 17:36 ` bugzilla at busybox.net
2011-01-10 23:14 ` 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-2869-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