All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults.
Date: Mon, 14 Nov 2005 17:45:44 -0600	[thread overview]
Message-ID: <200511141745.44703.rob@landley.net> (raw)
In-Reply-To: <200511141724.55055.rob@landley.net>

On Monday 14 November 2005 17:24, Rob Landley wrote:
> On Monday 14 November 2005 15:55, Jeff Dike wrote:
> > On Sun, Nov 13, 2005 at 05:32:10PM -0600, Rob Landley wrote:
> > > moan moan
>
> And proud of it!
>
> > Can you try the x86-64-clobbers-rcx patch below?
>
> Sure.  (Rummages...)
>
> > If you don't have it already, apply the fix-x86-stubs patch first.
>
> It said it was reversed, so I'm going to assume for the moment that
> 2.6.15-rc1 already has it, try the second...
>
> patching file arch/um/sys-i386/stub_segv.c
> Hunk #2 FAILED at 19.
> 1 out of 2 hunks FAILED -- saving rejects to file
> arch/um/sys-i386/stub_segv.c.rej
>
> Ok, fix that up by hand...  And the build breaks in stub_segv.c.
>
> What version are these patches against?  Let's try a straight 2.6.14...
>
> fix-x86-stubs applied cleanly.
> x86-64-clobbers-rcx...  Still fails hunk #2.
>
> Back off to a clean 2.6.14 again and try clobbers-rcx first...
>
> Still fails hunk #2.
>
> Rob

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:

 CC      arch/um/sys-x86_64/stub_segv.o
arch/um/sys-x86_64/stub_segv.c:7:24: asm/signal.h: Nie ma takiego pliku ani 
katalogu
In file included from /usr/include/linux/siginfo.h:1,
                 from /usr/include/asm-x86_64/siginfo.h:8,
                 from /usr/include/asm/siginfo.h:12,
                 from arch/um/sys-x86_64/stub_segv.c:10:
/usr/include/linux/signal.h:2:2: warning: #warning "You should include 
<signal.h>. This time I will do it for you."
In file included from /usr/include/signal.h:333,
                 from /usr/include/linux/signal.h:4,
                 from /usr/include/linux/siginfo.h:1,
                 from /usr/include/asm-x86_64/siginfo.h:8,
                 from /usr/include/asm/siginfo.h:12,
                 from arch/um/sys-x86_64/stub_segv.c:10:

And so on...  (The x86-64 server I'm borrowing is in poland, hence the weird 
file not found messages).

This is because the actual build line is this:

  gcc -Wp,-MD,arch/um/sys-x86_64/.stub_segv.o.d -Wall -Wundef 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common 
-ffreestanding -O2 -fomit-frame-pointer -D__arch_um__ -DSUBARCH=\"x86_64\" 
-Dvmap=kernel_vmap -Din6addr_loopback=kernel_in6addr_loopback 
-Iarch/um/include  
-I/srv/staff/rob/firmware-build/sources/packages/linux-2.6.14/arch/um/kernel/skas/include 
-fno-builtin -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -c -o 
arch/um/sys-x86_64/stub_segv.o arch/um/sys-x86_64/stub_segv.c

And neither the arch/um/include nor the arch/um/kernel/skas/include 
directories contain an "asm" symlink.

[rob@rg4 linux-2.6.14]$ find arch/um -name "asm"
[rob@rg4 linux-2.6.14]$

I have no idea if any of this helps...

Rob


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
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:[~2005-11-14 23:45 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 [this message]
2005-11-15  1:38             ` Jeff Dike
2005-11-15  2:18               ` Rob Landley
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=200511141745.44703.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 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.