linux-um archives
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] compile problem
Date: Tue, 12 Feb 2008 22:26:39 +0100	[thread overview]
Message-ID: <47B20F0F.3050401@gmail.com> (raw)
In-Reply-To: <20080211231812.GC10369@c2.user-mode-linux.org>

Hi,

<asm/types.h> declares u32 only if there's __KERNEL__ defined, which is not case
of UML compile.

I found out the ptrace-abi.h is changed in the 2.6.24.1 and differs with the Linus
tree among others with adding following structure:

struct ptrace_bts_config {
        /* requested or actual size of BTS buffer in bytes */
        u32 size;
        /* bitmask of below flags */
        u32 flags;
        /* buffer overflow signal */
        u32 signal;
        /* actual size of bts_struct in bytes */
        u32 bts_size;
};

so thats where the u32 cames from in the Linus' tree.

Now when I know why my Linus' tree wont compile, I'd like to know why yours does :)
(I used your patch regarding the foo function errors as well...)
Maybe I have smth wrong with my headers, I use following symlinks:

/usr/include/linux -> $(kernel)/include/linux
/usr/include/asm -> $(kernel)/include/asm-x86
/usr/include/asm-generic -> $(kernel)/include/asm-generic


thanks,
jirka


Jeff Dike wrote:
> On Sun, Feb 10, 2008 at 09:06:08PM +0100, Jiri Olsa wrote:
>> Hi,
>>
>> I have problem with last Linus' git tree:
>>
>> scripts/kconfig/conf -s arch/um/Kconfig
>>   SYMLINK arch/um/include/kern_constants.h
>>   SYMLINK arch/um/include/sysdep
>>   CHK     arch/um/include/uml-config.h
>>   UPD     arch/um/include/uml-config.h
>>   CC      arch/um/sys-i386/user-offsets.s
>> In file included from /usr/include/asm/ptrace.h:5,
>>                  from arch/um/sys-i386/user-offsets.c:7:
>> /usr/include/asm/ptrace-abi.h:92: error: expected specifier-qualifier-list before 'u32'
> 
> This looks like a bug in your headers.  ptrace-abi includes
> <asm/types.h>, apparently to get the likes of u32, but they're not
> there.
> 
>> arch/um/sys-i386/user-offsets.c: In function 'foo':
>> arch/um/sys-i386/user-offsets.c:20: error: 'struct sigcontext' has
>> no member named 'eip'
> 
> This is a bit of a problem.  You installed new headers, which have the
> 'e' removed from the register names, but I can't just change UML
> because that will break compilation on current hosts with existing
> headers.
> 
> 				Jeff
> 



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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:[~2008-02-12 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 20:06 [uml-devel] compile problem Jiri Olsa
2008-02-11 23:18 ` Jeff Dike
2008-02-12 21:26   ` Jiri Olsa [this message]
2008-02-13 17:43     ` Jeff Dike
2008-02-12  1:12 ` 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=47B20F0F.3050401@gmail.com \
    --to=olsajiri@gmail.com \
    --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