linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [PATCH]Modules support in 2.6: reaching the complete fix
Date: Thu, 18 Dec 2003 20:32:50 +0100	[thread overview]
Message-ID: <200312182032.50394.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200312180119.hBI1JBkS008102@ccure.user-mode-linux.org>

Alle 02:19, giovedì 18 dicembre 2003, Jeff Dike ha scritto:
> blaisorblade_spam@yahoo.it said:
> > If not, I can just patch this way scripts/Makefile.lib:
>
> This seems promising.  Can the new infrastructure be put in
> arch/um/Makefile?

I'm going to check... the variables are all set with = so it should work, but 
my problem is that it seems that the arch/um/Makefile is not included when it 
descends in sub-directories. However, even if it CAN be put there, I think 
this should NOT happen, and that it should be cleaned enough to be accepted 
in mainline. Why?
I think that it should have to be tuned for each release, and would not be 
likely to always be tunable(i.e. it could have to be re-engeneered if they 
change Makefile.lib enough). I don't use in fact an external interface of 
KBUILD, but I mingle inside its implementation(i.e. I violate encapsulation).

> This would isolate it nicely to UML since it's the only arch which needs
> it.

> Although, thinking about this some more, this isn't the right way to do it
> in the long run.  Ultimately, the userspace stuff will be confined to
> arch/um/os, along with the userspace CFLAGS.  So, the arch/um/os/Makefile
> will contain this nonsense, and nothing outside there will have to worry
> about it.

> So, if you want to sign up to a longer project, you might start moving the
> userspace stuff into arch/um/os-Linux instead of trying to fix the build.

I don't agree for "instead". I.e. I think that as the first thing this must be 
fixed, and then we will go hunting the bug for MODVERSIONS(it needs that we 
post-process userspace files).
After this, then I could do this user space change(I can't promise for now but 
I hope I'll be able); but it is a bit problematical because KBUILD isn't 
built to link objects from different directories.
Obviously I work for 2.6, not 2.4: clean-ups like this don't need duplicated 
effort. (And 2.6 is much more fun than 2.4, since it's all better).

Could symlink be accepted as a solution for this(i.e. a symlink from 
drivers/hostaudio_user.c to some file inside the os/ directory)?

In this case, the fix I'm writing is needed anyway and probably won't even 
need to be changed.

I'm now going to fix the various Makefiles and post the complete fix, since it 
it at least promising.

Bye
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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

  reply	other threads:[~2003-12-18 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-13 17:28 [uml-devel] [PATCH]Modules support in 2.6: reaching the complete fix BlaisorBlade
2003-12-13 20:19 ` [uml-devel] " Jeff Dike
2003-12-14 15:04   ` BlaisorBlade
2003-12-17 17:51   ` BlaisorBlade
2003-12-18  1:19     ` Jeff Dike
2003-12-18 19:32       ` BlaisorBlade [this message]
2003-12-18 22:13         ` Jeff Dike
2003-12-19 19:51           ` BlaisorBlade
2003-12-23 19:31             ` 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=200312182032.50394.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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