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 3007] New: kexec doesn't build: Missing regdef.h file
Date: Wed, 22 Dec 2010 23:20:23 +0000 (UTC)	[thread overview]
Message-ID: <bug-3007-163@https.bugs.busybox.net/> (raw)

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

           Summary: kexec doesn't build:  Missing regdef.h file
           Product: buildroot
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: andy.kennedy at adtran.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Target is mips-32r2

kexec/arch/mips/mips-setup-simple.S:17:20: fatal error: regdef.h: No such file
or directory
compilation terminated.


Simple fix is to copy the file from
output/toolchain/uClibc-0.9.31/libc/sysdeps/linux/mips/sys/regdef.h

to:
output/build/kexec-2.0.1/kexec/arch/mips/include

-- 
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:[~2010-12-22 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 23:20 bugzilla at busybox.net [this message]
2010-12-28 22:59 ` [Buildroot] [Bug 3007] kexec doesn't build: Missing regdef.h file bugzilla at busybox.net
2010-12-30 16:02   ` ANDY KENNEDY
2010-12-30 16:15     ` Gustavo Zacarias
2010-12-30 18:15       ` ANDY KENNEDY
2010-12-31  0:22         ` Gustavo Zacarias
2011-01-14 22:09 ` 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-3007-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.