linux-um archives
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] build error of an UML kernel with 2.6.2x sources
Date: Sun, 19 Aug 2007 18:12:33 +0200	[thread overview]
Message-ID: <200708191812.35947.toralf.foerster@gmx.de> (raw)
In-Reply-To: <20070819155746.GA5896@c2.user-mode-linux.org>


[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]

Am Sonntag, 19. August 2007 schrieb Jeff Dike:
> On Sun, Aug 19, 2007 at 11:42:55AM +0200, Toralf Förster wrote:
> > arch/um/sys-i386/user-offsets.c:7:22: error: asm/user.h: No such file or directory
> > arch/um/sys-i386/user-offsets.c: In function 'foo':
> > arch/um/sys-i386/user-offsets.c:51: error: invalid application of 'sizeof' to incomplete type 'struct user_i387_struct'
> 
> What's the host distro?

Im using Gentoo Linux with sys-kernel/linux-headers-2.6.21 and
the kernel sys-kernel/gentoo-sources-2.6.22-r4 (== 2.6.22.3 + Gentoo specific
patches)

> Do you have either user_i387_struct or elf_fpregset_t anywhere in your
> /usr/include?   If not, then your headers are broken, as there is no
> way to use PTRACE_GETFPREG since you can't tell how big a buffer to
> pass in.
I found a definition of elf_fpregset_t within incluce files from the glibc
package:

tfoerste@n22 /usr/include $ grep -Hir user_i387_struct *

tfoerste@n22 /usr/include $ grep -Hir elf_fpregset_t *
sys/procfs.h:typedef struct user_fpregs_struct elf_fpregset_t;
sys/procfs.h:typedef elf_fpregset_t prfpregset_t;

tfoerste@n22 /usr/include $ equery b sys/procfs.h
[ Searching for file(s) sys/procfs.h in *... ]
sys-libs/glibc-2.5-r4 (/usr/include/sys/procfs.h)


-- 
MfG/Sincerely

Toralf Förster

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-08-19 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19  9:42 [uml-devel] build error of an UML kernel with 2.6.2x sources Toralf Förster
2007-08-19 15:57 ` Jeff Dike
2007-08-19 16:12   ` Toralf Förster [this message]
2007-08-20 14:11     ` Jeff Dike
2007-08-20 15:55       ` Daniel Gryniewicz
     [not found]       ` <200708201730.37648.toralf.foerster@gmx.de>
2007-08-20 16:05         ` Jeff Dike
2007-10-06 13:14           ` Toralf Förster
2007-10-08 15:04             ` Jeff Dike
     [not found]               ` <200710081759.33242.toralf.foerster@gmx.de>
2007-10-09 16:44                 ` Jeff Dike

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=200708191812.35947.toralf.foerster@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.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