linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@gentoo.org
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails
Date: Wed, 09 Feb 2005 21:58:01 +0000	[thread overview]
Message-ID: <E1CyzqT-00064s-Mn@nuthatch.gentoo.org> (raw)

http://bugs.gentoo.org/show_bug.cgi?id=49277





------- Additional Comments From blaisorblade_spam@yahoo.it  2005-02-09 13:58 PST -------
Yes, upgrading would partially help. Alternatively, using a non-NPTL glibc is a workaround (but things get slower); using the latest, ~x86 glibc, built without the nptlonly flag, makes sure that UML is linked against a non-NPTL glibc, so this is also a workaround.

In short, see my previous message, and note that the previous official source (Jeff Dike) for the portage releases has stopped doing releases, since main work happens onto vanilla kernels (UML has been merged into vanilla Linux, finally). He now only maintains a development tree (http://user-mode-linux.sourceforge.net/patches.html, if you want, but it's for development).

Both the 2.6.9-bs6 patchset (which I maintain and is very stable, see at http://www.user-mode-linux.org/~blaisorblade/) and the vanilla 2.6.10 Linux kernel (with a bit of other problems, which are fixed in the upcoming vanilla 2.6.11) have the (partial) fix included: they work if you compile a SKAS-only UML (enable CONFIG_SKAS and disable CONFIG_TT).

Everything fails to compile if you have a NPTL glibc in /lib (necessary condition to experience the bug) and UML is statically linked, i.e. you enable also TT mode or explicitly request static linking (which is implied by TT mode).

For this configuration, no workaround exists at the moment, nor I know anyone who knows enough about linking scripts and glibc details to fix it.
And note that enabling TT mode is required to run UML onto a vanilla Linux kernel as host system; with the SKAS patch on the host it is possible to run a UML built with only SKAS mode enabled and TT mode disabled.

* Why wasn't the portage tree not updated (I guess):
The reason is that while previously UML was a separate patch to apply to a vanilla tarball, while starting from 2.6.9 UML has been merged in mainline so a vanilla kernel (should) compile. However, a vanilla 2.6.9 kernel tarball contains the whole UML architecture, but has these problems (they were discovered and fixed later).

I release (when needed) a patchset (the -bb/-bs one) against vanilla kernels, however, for further UML fixes. "When needed" means that if the mainline release is good, and no important fixes are written, or if my time is short, I don't do a release.

Possibly including it inside the portage tree would be good (as usermode-bb-sources, if you want). I both use a Gentoo system and maintain that patchset, so if you want I can help for this.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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:[~2005-02-09 21:58 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 21:58 bugzilla-daemon [this message]
     [not found] <bug-49277@bugs.gentoo.org>
2005-06-07  0:57 ` [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails bugzilla-daemon
2005-06-07 14:31   ` Nix
2005-06-07 14:52     ` Blaisorblade
2005-06-07 15:54       ` Nix
2005-06-07 16:11         ` Blaisorblade
2005-06-07 16:21           ` Nix
2005-06-07 16:44             ` Blaisorblade
2005-06-07 19:47               ` Nix
2005-06-08  0:34                 ` Blaisorblade
2005-06-08 17:38                   ` Nix
2005-06-08 18:10                     ` Blaisorblade
2005-06-09 22:08                   ` Blaisorblade
2005-06-07 16:52             ` Blaisorblade
2005-06-07 16:02       ` Nix
2005-07-06  9:57 ` bugzilla-daemon
2005-07-06 16:22 ` bugzilla-daemon
2005-07-09 22:41 ` bugzilla-daemon
2005-07-12 17:13 ` bugzilla-daemon
2005-07-13 15:14 ` bugzilla-daemon
2005-07-14  8:11 ` bugzilla-daemon
2005-07-14 19:57   ` Rob Landley
2005-07-14 20:22     ` Rob Landley
2005-07-14  8:12 ` bugzilla-daemon
2005-07-14  8:39 ` bugzilla-daemon
2005-07-14  8:40 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2005-05-08 11:55 bugzilla-daemon
2005-04-30  0:41 bugzilla-daemon
2005-04-28 16:26 bugzilla-daemon
2005-04-13 15:50 bugzilla-daemon
2005-04-08 18:01 bugzilla-daemon
2005-03-19 20:54 bugzilla-daemon
2005-03-02 23:28 bugzilla-daemon
2005-03-02 15:04 bugzilla-daemon
2005-02-18 13:05 bugzilla-daemon
2005-02-09 15:38 bugzilla-daemon
2005-02-10  3:40 ` Rob Landley
2005-02-10 11:31   ` Blaisorblade
2005-02-10 14:16     ` Rob Landley
2005-02-10 15:44       ` Blaisorblade
2005-02-11  0:31         ` Rob Landley
2005-02-11  2:33           ` Blaisorblade
2005-02-11  2:42             ` Rob Landley
2005-02-11  3:48               ` Blaisorblade
2005-01-12  1:24 bugzilla-daemon

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=E1CyzqT-00064s-Mn@nuthatch.gentoo.org \
    --to=bugzilla-daemon@gentoo.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;
as well as URLs for NNTP newsgroup(s).