From: Rob Landley <rob@landley.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults.
Date: Mon, 14 Nov 2005 20:18:31 -0600 [thread overview]
Message-ID: <200511142018.32074.rob@landley.net> (raw)
In-Reply-To: <20051115013855.GA12719@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Monday 14 November 2005 19:38, Jeff Dike wrote:
> On Mon, Nov 14, 2005 at 05:45:44PM -0600, Rob Landley wrote:
> > The breakage, by the way, (which occurs when you fix the failing hunk #2
> > up by hand) stems from the inability to find asm/signal.h:
>
> What distro is this? asm/signal is in glibc-kernheaders here:
>
> % rpm -q -f /usr/include/asm/signal.h
> glibc-kernheaders-2.4-9.1.94
Well, according to /proc/version, it's PLD:
Linux version 2.6.11.10-6 (builder@serwus) (gcc version 3.3.5 (PLD Linux)) #1
Fri May 27 20:55:12 UTC 2005
rpm has a package "basesystem" that's version 1.99.
Here's their web page: http://www.pld.org.pl/
I think this is the distro Maszur originally did his linux-libc-headers
package for, so I'm guessing that's what they're using. (Not the glibc
stuff.) I use uClibc a lot elsewhere, and that generally uses Mazur's
headers rather than the glibc ones too.
It has:
[rob@rg4 include]$ find /usr/include -name signal.h
/usr/include/linux/signal.h
/usr/include/signal.h
/usr/include/sys/signal.h
Hmm, I'm somewhat familiar with Mazur's headers and may be able to fix this
up...
Ok, the attached patch builds for me. (I didn't say it was _right_, I said it
builds. :)
And let's see how it runs...
Nope, same failure. Want the new panic and register dump?
[-- Attachment #2: headers.patch --]
[-- Type: text/x-diff, Size: 466 bytes --]
--- linux-2.6.15-rc1/arch/um/sys-x86_64/stub_segv.c 2005-11-14 23:20:54.855517272 +0100
+++ linux-2.6.14/arch/um/sys-x86_64/stub_segv.c 2005-11-15 03:11:28.580804656 +0100
@@ -4,11 +4,9 @@
*/
#include <linux/compiler.h>
-#include <asm/signal.h>
+#include <signal.h>
#include <asm/unistd.h>
#include <asm/sigcontext.h>
-#include <asm/siginfo.h>
-#include <asm/ucontext.h>
#include "uml-config.h"
#include "sysdep/sigcontext.h"
#include "sysdep/faultinfo.h"
next prev parent reply other threads:[~2005-11-15 2:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 1:36 [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults Rob Landley
2005-11-13 17:54 ` Blaisorblade
2005-11-13 23:26 ` Rob Landley
2005-11-14 19:40 ` Blaisorblade
2005-11-16 3:09 ` Rob Landley
2005-11-18 7:43 ` Blaisorblade
2005-11-18 7:36 ` Rob Landley
2005-11-18 7:58 ` Blaisorblade
2005-11-18 8:58 ` Rob Landley
2005-11-19 0:11 ` [uml-devel] [PATCH] UML x86-64 build fix Rob Landley
2005-11-13 19:32 ` [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults Jeff Dike
2005-11-13 19:20 ` Blaisorblade
2005-11-13 23:32 ` Rob Landley
2005-11-14 15:33 ` Jeff Dike
2005-11-14 21:55 ` Jeff Dike
2005-11-14 23:24 ` Rob Landley
2005-11-14 23:45 ` Rob Landley
2005-11-15 1:38 ` Jeff Dike
2005-11-15 2:18 ` Rob Landley [this message]
2005-11-15 22:09 ` Paolo Giarrusso
2005-11-16 0:57 ` 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=200511142018.32074.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--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