linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Nix <nix@esperi.org.uk>
Subject: Re: [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails
Date: Tue, 7 Jun 2005 18:11:51 +0200	[thread overview]
Message-ID: <200506071811.52440.blaisorblade@yahoo.it> (raw)
In-Reply-To: <87is0q5fik.fsf@amaterasu.srvr.nix>

On Tuesday 07 June 2005 17:54, Nix wrote:
> On Tue, 7 Jun 2005, blaisorblade@yahoo.it said:
> > On Tuesday 07 June 2005 16:31, Nix wrote:
> >> On Tue, 07 Jun 2005, bugzilla-daemon@gentoo.org gibbered uncontrollably:
> >> > Ok, I hope there is still somebody using UML on a NPTL-only system.
> >> > The workaround suggested last time was to avoid enabling
> >> > CONFIG_MODE_TT; now I think I've got over this problem, too. So, when
> >> > I release 2.6.11.8-bs6 (which will happen very shortly, I hope), I'd
> >> > like to get some testing from you about this issue.
> >>
> >> I can give it a try if you like.
> >>
> >> (That's a MODE_TT build on a system with NPTL headers, right?)
> >
> > With NPTL-only glibc, I meant (and I guess you mean too).

> Well, I've got a dual non-NPTL glibc in /lib and NPTL glibc in /lib/tls,
> but I can force use of either,
Even for static linking? In this case, strange setup. If dynamic linking, it 
already worked, when you used dynamic linking i.e. disabled SKAS.
> and the headers, 
Different headers too? I didn't know that (and it makes me suspicious about 
binary compatibility).
> the dynamic loader, and 
> everything other than the stuff in /lib come from the NPTL glibc build.
> This is pretty much indistinguishable from a pure-NPTL system unless
> you force LD_ASSUME_KERNEL, which I'm not.
>
> > Just give me the time to actually upload the tree, which I'm doing at the
> > moment, and forgive me if I added anything ruining the compilation while
> > I was working on x86_64 host.
> >
> > Ok, done... enjoy!
>
> This is
> <http://www.user-mode-linux.org/~blaisorblade/patches/guest/uml-2.6.11.8-bs
>6/uml-2.6.11.8-bs6.patch.bz2>, right?

Not sure about that... I uploaded and destroyed it multiple times, so here's 
the MD5 of the current version:

md5sum uml-2.6.11.8-bs6.patch.bz2
1a6868d70c7af75f3375eba3b7dfd466  uml-2.6.11.8-bs6.patch.bz2

>(It looks like it was uploaded only a 
> few minutes ago in some time zone quite divergent from either of ours. :) )
Hmm, the first upload was done during this night, so I guess it was not a 
timezone problem but an actual crazy boy fixing sucking compile errors at a 
late time.
-- 
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: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
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-06-07 16:08 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2005-05-08 11:55 bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
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 21:58 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=200506071811.52440.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=nix@esperi.org.uk \
    --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