From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003064]: strace build on MIPS - w. kernel 2.6.15
Date: Tue, 22 Apr 2008 08:51:47 -0700 [thread overview]
Message-ID: <5d682f294967fff366f1086d1410b882@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3064
======================================================================
Reported By: glavepp
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3064
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-22-2008 08:51 PDT
Last Modified: 04-22-2008 08:51 PDT
======================================================================
Summary: strace build on MIPS - w. kernel 2.6.15
Description:
I'm building "strace" on mips, using directly the kernel headers from the
2.6.15 kernel (I don't know if this is a good practice...).
In this case, I cannot build, because of a different declaration of the
"struct sigcontext".
The attached patch solves the problem.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
04-22-08 08:51 glavepp New Issue
04-22-08 08:51 glavepp Status new => assigned
04-22-08 08:51 glavepp Assigned To => buildroot
04-22-08 08:51 glavepp File Added: strace-mips-sigcontext-kernel26.patch
======================================================================
reply other threads:[~2008-04-22 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5d682f294967fff366f1086d1410b882@busybox.net \
--to=bugs@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