From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001537]: kexec doesn't build for arm/armeb
Date: Fri, 19 Oct 2007 23:32:56 +0200 [thread overview]
Message-ID: <20071019213256.GA1593@aon.at> (raw)
In-Reply-To: <a1a26c05871e60062b21dcb76a88bbe1@busybox.net>
On Wed, Oct 17, 2007 at 10:27:31PM -0700, bugs at busybox.net wrote:
>
>The following issue has been RESOLVED.
Ulf,
If you close a bug, then please CLOSE it, so it doesn't show up as not
closed in mantis.
There are a couple of these that you have to CLOSE. Please do..
Thanks.
>======================================================================
>http://busybox.net/bugs/view.php?id=1537
>======================================================================
>Reported By: hmoffatt
>Assigned To: buildroot
>======================================================================
>Project: buildroot
>Issue ID: 1537
>Category: Architecture Specific
>Reproducibility: always
>Severity: minor
>Priority: normal
>Status: resolved
>Resolution: fixed
>Fixed in Version:
>======================================================================
>Date Submitted: 10-16-2007 22:32 PDT
>Last Modified: 10-17-2007 22:27 PDT
>======================================================================
>Summary: kexec doesn't build for arm/armeb
>Description:
>kexec doesn't build on arm or armeb.
>
>Problems are:
>1. armeb not a supported architecture;
>2. arm support patch needs to be updated due to an internal API change.
>
>Fix is trivial - attached.
>======================================================================
>
>----------------------------------------------------------------------
> hmoffatt - 10-17-07 21:43
>----------------------------------------------------------------------
>Use kexec-arm-fix2 instead. It fixes the incorrect syscall number in the
>original source.
>
>----------------------------------------------------------------------
> UlfSamuelsson - 10-17-07 22:27
>----------------------------------------------------------------------
>kexec-arm-fix2 has been applied in revision 20278
>
>Issue History
>Date Modified Username Field Change
>======================================================================
>10-16-07 22:32 hmoffatt New Issue
>10-16-07 22:32 hmoffatt Status new => assigned
>10-16-07 22:32 hmoffatt Assigned To => buildroot
>10-16-07 22:33 hmoffatt File Added: kexec-arm-fix
>10-17-07 21:42 hmoffatt File Added: kexec-arm-fix2
>10-17-07 21:43 hmoffatt Note Added: 0002831
>10-17-07 22:27 UlfSamuelsson Status assigned => resolved
>10-17-07 22:27 UlfSamuelsson Resolution open => fixed
>10-17-07 22:27 UlfSamuelsson Note Added: 0002832
>======================================================================
>
>_______________________________________________
>buildroot mailing list
>buildroot at uclibc.org
>http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2007-10-19 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 5:27 [Buildroot] [buildroot 0001537]: kexec doesn't build for arm/armeb bugs at busybox.net
2007-10-19 21:32 ` Bernhard Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-30 21:44 bugs at busybox.net
2007-10-18 4:43 bugs at busybox.net
2007-10-17 5:33 bugs 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=20071019213256.GA1593@aon.at \
--to=rep.dot.nop@gmail.com \
--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.