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 5948] New: AT91 Bootstrap3 defconfig name change not detected (by make process)
Date: Sat, 16 Feb 2013 17:34:32 +0000 (UTC)	[thread overview]
Message-ID: <bug-5948-163@https.bugs.busybox.net/> (raw)

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

           Summary: AT91 Bootstrap3 defconfig name change not detected (by
                    make process)
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: peter.stosz at mentat.hu
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When I set first time Bootloaders/AT91 Bootstrap 3:Defconfig name (for example
at91sam9260df), the process download and compile the requested binary. But when
I change the defonfig name (for example to at91sam9260nf), nothing to do.
After I purge manually the output/build/at91bootstrap3-3.2, the compilation
well done.

BR=2013.02-rc1
OS=deb6_32bit

-- 
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:[~2013-02-16 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16 17:34 bugzilla at busybox.net [this message]
2013-02-17  2:52 ` [Buildroot] [Bug 5948] AT91 Bootstrap3 defconfig name change not detected (by make process) 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-5948-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.