linux-um archives
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Julian Scheid <julian@sektor37.de>
Cc: jdike@karaya.com, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Default kernel configuration on 2.6.x
Date: Mon, 11 Oct 2004 18:58:45 -0400	[thread overview]
Message-ID: <23090.1097535525@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Julian Scheid <julian@sektor37.de>  of "Tue, 12 Oct 2004 00:22:36 +0200." <416B07AC.3030308@sektor37.de>

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Julian" == Julian Scheid <julian@sektor37.de> writes:
    Julian> Therefore I think it would make sense to have the UML
    Julian> patches for the affected kernel versions remove the second
    Julian> through fourth element from conf_confnames (as shown above)
    Julian> so that the build will immediately fall back to
    Julian> arch/um/defconfig if .config isn't found, always ignoring
    Julian> status quo configuration files on the host. A corresponding
    Julian> patch for 2.6.8.1 is attached.

  I have a better suggestion.
  Make it ignore those suggestions *COMPLETELY* when
       $ARCH != `uname -m`
       $SUBARCH != `uname -m`

  Since those suggestions are wrong for all cross-compilation as well,
and this is a form of cross-compilation.

  {well, uname -m is wrong. I never did find a standard utility that
returned 'i386'. arch -k used to do the right thing on SunOS, but it
never did the right thing on any Linux distro}

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQWsQI4qHRg3pndX9AQFNvwP/SUpnojGHN+hcbkmH4+ZOM1mdlEfQq+tF
1f9eCfgx8lzv7wIn/HqFsHJlNEWChDr+ZCBNF2ibS9kOvGbnv1HZIHKI+ETZVhFE
FAVawdmLCVGwLZJxBnDKwZZ01Xdh3C4f3Pp6KgDyq32L0cE04bEqZR1qk4jg/NlJ
GttyxuUdCnQ=
=aeH+
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-11 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 22:22 [uml-devel] Default kernel configuration on 2.6.x Julian Scheid
2004-10-11 22:58 ` Michael Richardson [this message]
2004-10-11 23:47   ` BlaisorBlade
2004-10-11 23:46 ` BlaisorBlade
2004-10-12  0:41   ` Julian Scheid
2004-10-12  1:01     ` BlaisorBlade
2004-10-12  1:39       ` Julian Scheid

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=23090.1097535525@marajade.sandelman.ottawa.on.ca \
    --to=mcr@sandelman.ottawa.on.ca \
    --cc=jdike@karaya.com \
    --cc=julian@sektor37.de \
    --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