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 8771] New: make savedefconfig modifies sources
Date: Mon, 07 Mar 2016 18:43:49 +0000	[thread overview]
Message-ID: <bug-8771-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 8771
           Summary: make savedefconfig modifies sources
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: geoff at infradead.org
                CC: buildroot at uclibc.org
  Target Milestone: ---

When building out of the source tree 'make savedefconfig' will modify the
sources in some situations.  This is problematic when the sources are on
read-only media.  It should write to the file defconfig in the build directory.

  mkdir /tmp/out
  make O=/tmp/out qemu_aarch64_virt_defconfig
  cd /tmp/out
  make savedefconfig

In this case qemu_aarch64_virt_defconfig in the sources gets modified.

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

             reply	other threads:[~2016-03-07 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 18:43 bugzilla at busybox.net [this message]
2016-03-07 20:23 ` [Buildroot] [Bug 8771] make savedefconfig modifies sources bugzilla at busybox.net
2016-03-07 23:39   ` Arnout Vandecappelle
2016-03-08  8:06     ` Thomas Petazzoni
2016-03-08 11:36       ` Peter Korsgaard
2016-03-08 17:01       ` Steve Calfee
2016-03-08 17:38         ` Arnout Vandecappelle
2016-03-08 18:06           ` Steve Calfee

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-8771-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 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.