From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Getting the x86-64 rollup patch to work on my x86 laptop.
Date: Fri, 18 Nov 2005 08:26:53 +0100 [thread overview]
Message-ID: <200511180826.53596.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200511180048.06213.rob@landley.net>
On Friday 18 November 2005 07:48, Rob Landley wrote:
> On Thursday 17 November 2005 21:12, Jeff Dike wrote:
> > On Thu, Nov 17, 2005 at 04:51:33PM -0600, Rob Landley wrote:
> > > find . -name asm
> > This all looks the same as I have here, except for the asm-i386 thing,
> > which I don't think matters. ldt.h seems to be at the center of this,
> > so can you check the following:
> > asm-i386/ldt.h contains a struct user_desc
> Yup.
> > asm-um includes asm/arch/ldt.h
> There's no asm subdirectory under asm-um.
Jeff meant that inside asm-um you should have a "arch" symlink to
"../asm-i386", and that include/asm/arch/ldt.h should exist (in the source
tree root).
> > asm-um/ldt.h contains a typedef of uml_ldt_t
> asm-um/ldt.h is a 0 byte file.
Damnit! Do rm on it and things will work (Makefiles will create a symlink to
ldt-$(SUBARCH) in its place). We had this problem in the past, and exactly
for a mis-formed patch with quilt.
> > mmu-skas.h includes asm-um/ldt.h
> The one in arch/um/include/skas includes asm/ldt.h
> The one in arch/um/kernel/skas/include is a 0 byte file.
I suppose that's a rename from something in the patchset... and that the file
is not properly deleted (I hope this one shouldn't create problems).
Damn it again! Je-eff? I remember quilt can be taught to do it!
> > Also, generate a .i for the C file that's being built and check that
> > the definitions are getting pulled in. There may be an easier way to
> > do this, but I
I do make ARCH=um $path.i is supposed to work. I recently fixed it (should be
upstream) up for userspace files (along with other extensions - .lst, .s and
so on) . Before, obviously, I did as you do.
> > turn on V=1
> > cd obj
> > paste the gcc command into an xterm
> > edit it as follows
> > the -o -c foo.o is replaced by -E
> > add > x.i at the end
> The line that's going boing is
> gcc -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
> -fno-common -ffreestanding -O2 -fomit-frame-pointer -D__arch_um__
> -DSUBARCH=\"i386\" -Iarch/um/include
> -I/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/include
> -I/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/include
>/skas -Dvmap=kernel_vmap -Din6addr_loopback=kernel_in6addr_loopback
> -Derrno=kernel_errno -Dsigprocmask=kernel_sigprocmask -U__i386__ -Ui386
> -mpreferred-stack-boundary=2 -D_LARGEFILE64_SOURCE -nostdinc
> -isystem /usr/lib/gcc-lib/i486-linux/3.3.5/include -D__KERNEL__ -Iinclude
> -Iinclude2
> -I/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/include
> -include include/linux/autoconf.h -S -o
> arch/um/kernel-offsets.s
> /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/sys-i386/
>kernel-offsets.c
> I don't even have to add V=1 to get it, that sucker isn't run through a
> prettification macro. However, whey you say "-o -c foo.o", I can't find
> that to replace it with -E. Do you mean the "-S -o kernel-offsets.s" bit?
In this case yes - Jeff thought the build would stop when building a "foo.o",
but it's stopping earlier than he expected.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
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_idv28&alloc_id\x16845&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-18 7:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 17:00 [uml-devel] Getting the x86-64 rollup patch to work on my x86 laptop Rob Landley
2005-11-16 19:42 ` Bodo Stroesser
2005-11-16 22:19 ` Jeff Dike
2005-11-17 0:11 ` Rob Landley
2005-11-17 5:26 ` Jeff Dike
2005-11-17 13:16 ` Rob Landley
2005-11-17 16:37 ` Jeff Dike
2005-11-17 15:58 ` Rob Landley
2005-11-17 17:26 ` Jeff Dike
2005-11-17 17:40 ` Jeff Dike
2005-11-17 22:19 ` Rob Landley
2005-11-17 14:46 ` Rob Landley
2005-11-17 17:24 ` Jeff Dike
2005-11-17 18:40 ` Jeff Dike
2005-11-17 22:51 ` Rob Landley
2005-11-17 23:12 ` Rob Landley
2005-11-18 3:12 ` Jeff Dike
2005-11-18 6:14 ` Rob Landley
2005-11-18 6:32 ` Rob Landley
2005-11-18 6:48 ` Rob Landley
2005-11-18 7:26 ` Blaisorblade [this message]
2005-11-18 7:33 ` Rob Landley
2005-11-18 7:58 ` Blaisorblade
2005-11-18 8:59 ` Rob Landley
2005-11-19 2:35 ` Blaisorblade
2006-01-11 21:52 ` [uml-devel] tls incrementals for 2.6.15 breaking build ... still? D. Bahi
2006-01-12 5:29 ` D. Bahi
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=200511180826.53596.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=rob@landley.net \
--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