From: Oleg Drokin <green@namesys.com>
To: Jeff Dike <jdike@karaya.com>
Cc: Mike Anderson <andmike@us.ibm.com>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: uml-patch-2.5.42-1
Date: Tue, 15 Oct 2002 17:05:58 +0400 [thread overview]
Message-ID: <20021015170558.A6060@namesys.com> (raw)
In-Reply-To: <200210151352.IAA02057@ccure.karaya.com>
Hello!
On Tue, Oct 15, 2002 at 08:52:17AM -0500, Jeff Dike wrote:
> > For some reason I now need this patch to make bk-current to compile
> That patch is against stock 2.5.42, so I don't make any guarantees about
> bk-current.
I am in no way inplying that you are making any guarantees about your patches to
work with something but the kernels they are released for.
On the other hand I thought you might find it useful if I report to you
problems with more modern kernels that I encounter so that when you will
update UML to never kernel you do not need to hit all the problems by yourself.
> However the __i386__ thing should be taken care of by Makefile-i386 doing
> CFLAGS += -U__i386__
> I might have messed up the patch, I'll check and fix it if so.
Yes, it seems to be the case.
CFLAGS is defined first in arch/um/Makefile and only then you do
include Makefile-{SUBARCH}
Moving 'include $(ARCH_DIR)/Makefile-$(SUBARCH)' in front of CFLAGS
helped.
Bye,
Oleg
next prev parent reply other threads:[~2002-10-15 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 0:58 uml-patch-2.5.42-1 Jeff Dike
2002-10-15 6:42 ` uml-patch-2.5.42-1 Oleg Drokin
2002-10-15 7:25 ` [uml-devel] uml-patch-2.5.42-1 Mike Anderson
2002-10-15 13:52 ` uml-patch-2.5.42-1 Jeff Dike
2002-10-15 13:05 ` Oleg Drokin [this message]
2002-10-15 14:00 ` [uml-devel] uml-patch-2.5.42-1 Mike Anderson
2002-10-15 15:51 ` Jeff Dike
2002-10-15 12:00 ` uml-patch-2.5.42-1 Oleg Drokin
2002-10-15 16:25 ` uml-patch-2.5.42-1 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=20021015170558.A6060@namesys.com \
--to=green@namesys.com \
--cc=andmike@us.ibm.com \
--cc=jdike@karaya.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