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 5234] New: kexec fails to build
Date: Sat, 19 May 2012 23:57:32 +0000 (UTC)	[thread overview]
Message-ID: <bug-5234-163@https.bugs.busybox.net/> (raw)

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

           Summary: kexec fails to build
           Product: buildroot
           Version: 2012.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: baruch at ev-en.org
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 4358
  --> https://bugs.busybox.net/attachment.cgi?id=4358
patch to make kexec compile in cross-builds

Building kexec as part of buildroot with the uclibc library I get that the
bin-to-hex utility fails to build, this is because it requires libc.so.0 which
is not available on the host and is only generated as part of the buildroot
tree. To overcome this kexec needs to build bin-to-hex with the HOSTCC. I've
noticed that this was a patch in buildroot which was dropped at some point. So
I recreated it, I also sent it to upstream kexec-tools mailing list and hope it
will be accepted for future versions.

The patch as needed for buildroot is attached, it needs to be dropped into
packages/kexec/

-- 
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:[~2012-05-19 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 23:57 bugzilla at busybox.net [this message]
2012-10-16  2:16 ` [Buildroot] [Bug 5234] kexec fails to build bugzilla at busybox.net
2013-05-26 14:25 ` 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-5234-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