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 499] New: make O=... busybox-menuconfig crashes
Date: Wed, 29 Jul 2009 15:00:40 +0000 (UTC)	[thread overview]
Message-ID: <bug-499-163@https.bugs.busybox.net/> (raw)

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

           Summary: make O=... busybox-menuconfig crashes
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: thomas.petazzoni at free-electrons.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


make busybox-menuconfig crashes when used with the out-of-tree option O=:

#
# using defaults found in .config
#

interrupted(11)
make[3]: *** [menuconfig] Error 1
make[2]: *** [menuconfig] Error 2
make[2]: Leaving directory
`/home/thomas/local/buildroot-basic/project_build_arm/uclibc/busybox-1.14.2'
make[1]: *** [busybox-menuconfig] Error 2
make[1]: Leaving directory `/home/thomas/local/buildroot'

Interestingly, manually doing

make __TARGET_ARCH=arm -C
/path/to/the/build/directory/project_build_arm/uclibc/busybox-1.14.2 menuconfig

works nicely. So it's the fact that it's been run by the Buildroot
infrastructure that makes it crash.


-- 
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:[~2009-07-29 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 15:00 bugzilla at busybox.net [this message]
2009-07-29 18:39 ` [Buildroot] [Bug 499] make O=... busybox-menuconfig crashes bugzilla at busybox.net
2009-08-31  7:51 ` bugzilla at busybox.net
2009-09-14 18:37 ` 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-499-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