From: Rob Landley <rob@landley.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/4] UML - Eliminate anonymous union and clean up symlink lossage
Date: Fri, 18 Nov 2005 01:03:29 -0600 [thread overview]
Message-ID: <200511180103.29950.rob@landley.net> (raw)
In-Reply-To: <200511172110.jAHLAQoe010199@ccure.user-mode-linux.org>
On Thursday 17 November 2005 15:10, Jeff Dike wrote:
> This gives a name to the anonymous union introduced in
> skas-hold-own-ldt, allowing to build on a wider range of gccs.
Or narrower range, in the case of Ubuntu "Horny Hedgehog". 2.6.15-rc1 builds
fine by itself, or with just patch 1 in this series, but with patch 2...
CHK include/linux/version.h
UPD include/linux/version.h
SYMLINK include/asm -> include/asm-um
SPLIT include/linux/autoconf.h -> include/config/*
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/kernel/skas/include
-Dvmap=kernel_vmap -Din6addr_loopback=kernel_in6addr_loopback
-Derrno=kernel_errno -Dsigprocmask=kernel_sigprocmask -U__i386__ -Ui386
-march=i686 -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
In file included
from /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/include/um_mmu.h:17,
from include2/asm/mmu.h:9,
from /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/include/linux/sched.h:23,
from /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/sys-i386/kernel-offsets.c:3:
/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/kernel/skas/include/mmu-skas.h:19:
error: syntax error before "uml_ldt_t"
/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/kernel/skas/include/mmu-skas.h:19:
warning: no semicolon at end of struct or union
In file included from include2/asm/mmu.h:9,
from /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/include/linux/sched.h:23,
from /home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/sys-i386/kernel-offsets.c:3:
/home/landley/newbuild/firmware-build/tmpdir/linux-2.6.14/arch/um/include/um_mmu.h:25:
error: field `skas' has incomplete type
make[2]: *** [arch/um/kernel-offsets.s] Error 1
make[1]: *** [_all] Error 2
make: *** [all] Error 2
next prev parent reply other threads:[~2005-11-18 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 21:10 [PATCH 2/4] UML - Eliminate anonymous union and clean up symlink lossage Jeff Dike
2005-11-18 7:03 ` Rob Landley [this message]
2005-11-18 7:10 ` [uml-devel] " Rob Landley
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=200511180103.29950.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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