From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Al Viro <viro@ftp.linux.org.uk>, Jeff Dike <jdike@addtoit.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
sam@ravnborg.org
Subject: Re: [uml-devel] Re: UML/2.6.14-rc3 doesn't work fixes
Date: Tue, 4 Oct 2005 12:26:36 +0200 [thread overview]
Message-ID: <200510041226.39233.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20051003233837.GA7992@ftp.linux.org.uk>
On Tuesday 04 October 2005 01:38, Al Viro wrote:
> On Mon, Oct 03, 2005 at 08:30:23PM +0200, Blaisorblade wrote:
> > The second is that, even if x86_64 uses things such as (from
> > arch/x86_64/mm/Makefile):
> >
> Err... Kbuild won't know what to do with your subarch-y. The way it works
> is simple - we are saying that e.g. bitops.o is a multi-part object with
> only one part, namely ../../i386/lib/bitops.o. Said part is built by the
> normal Kbuild logics and then we get (dummy) linking, creating bitops.o.
I know about kbuild, I just forgot to mention adding:
obj-y += subarch.o
(which you add below).
I've been cleaning up the UML Makefiles for almost a year, when I was even
more of a kernel newbie than I am now ;-)...
> > for most things (see arch/x86_64/oprofile/Makefile), and for highmem and
> > module I'd just do that by hand:
> >
> > highmem-y := $(SUBARCH_DIR)/mm/highmem.o
> > module-y := $(SUBARCH_DIR)/kernel/module.o
> >
> > with SUBARCH_DIR defined in arch/um/Makefile.
> Hrm... That just might be usable, _if_ we never run into modular suckers;
> in that case we can do the following:
> ifneq ($(subarch-objs-y),)
> obj-y += subarch.o
> subarch-y = $(addprefix ../../$(SUBARCH),$(subarch-objs-y))
> endif
> in arch/um/scripts/Makefile.rules with
>
> subarch-y = .....
> subarch-$(CONFIG_MODULE) += kernel/module.o
> etc. in arch/um/sys-.../Makefile
Hmm, yes, nice.
> The thing is, if we _ever_ need a potentially modular object pulled from
> the underlying architecture that trick will break.
We would just do them by hand, in this case. And say "don't use subarch-objs-y
for modular things".
In the existing case, I've pulled in the whole directory, since it had only
one module (aes-586.o).
Ah, I must add aes-x86_64 too, now it exists.
> So far we do not and
> since $(eval...) *is* a vile mess straight from the GNU intestine...
I do not fully agree about eval being evil, but I'm not gonna flame on this
issue...
--
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:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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-10-04 10:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 10:13 [uml-devel] UML/2.6.14-rc3 doesn't work fixes Blaisorblade
2005-10-02 11:38 ` [uml-devel] " Al Viro
2005-10-02 11:50 ` Blaisorblade
2005-10-02 17:32 ` Al Viro
2005-10-02 17:45 ` Blaisorblade
2005-10-02 15:51 ` Jeff Dike
2005-10-02 16:55 ` Al Viro
2005-10-02 18:01 ` Blaisorblade
2005-10-02 18:37 ` Al Viro
2005-10-02 20:54 ` Al Viro
2005-10-03 18:30 ` Blaisorblade
2005-10-03 23:38 ` Al Viro
2005-10-04 10:26 ` Blaisorblade [this message]
2005-10-04 11:09 ` Al Viro
2005-10-04 11:19 ` Blaisorblade
2005-10-04 11:55 ` Al Viro
2005-10-04 12:09 ` Blaisorblade
2005-10-04 17:09 ` Al Viro
2005-10-04 17:14 ` Al Viro
2005-10-04 17:18 ` Al Viro
2005-10-04 17:24 ` Al Viro
2005-10-04 17:28 ` Al Viro
2005-10-09 19:16 ` Blaisorblade
2005-10-03 18:56 ` Blaisorblade
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=200510041226.39233.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=sam@ravnborg.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@ftp.linux.org.uk \
--cc=viro@zeniv.linux.org.uk \
/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.