| To: | Aaron Lehmann <aaronl@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: linux-2.4-xfs build broken |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Mon, 9 Apr 2001 10:43:56 +0200 |
| Cc: | Andi Kleen <ak@xxxxxxx>, Russell Cattelan <cattelan@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20010409014147.C27832@vitelus.com>; from aaronl@vitelus.com on Mon, Apr 09, 2001 at 01:41:47AM -0700 |
| References: | <20010407161914.A4860@vitelus.com> <3ACFD59D.67BF49E1@thebarn.com> <20010409005723.A25023@vitelus.com> <20010409100516.A21515@gruyere.muc.suse.de> <20010409012728.A27832@vitelus.com> <20010409103219.B22252@gruyere.muc.suse.de> <20010409014147.C27832@vitelus.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Mon, Apr 09, 2001 at 01:41:47AM -0700, Aaron Lehmann wrote: > On Mon, Apr 09, 2001 at 10:32:19AM +0200, Andi Kleen wrote: > > Well, I had it several times in the past (early 2.1), and a make clean > > always cured it. Perhaps your tree is somehow corrupted? For XFS you > > could try a complete fresh checkout. > > That's exactly what I did when I encountered this... > > The first build on this fresh tree also failed this way, and no amount > of mrproper can seem to fix it. > > I'm mystified. Another possibility is a funny variant of loadkeys in your $PATH -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: linux-2.4-xfs build broken, Aaron Lehmann |
|---|---|
| Next by Date: | Re: linux-2.4-xfs build broken, Aaron Lehmann |
| Previous by Thread: | Re: linux-2.4-xfs build broken, Aaron Lehmann |
| Next by Thread: | Re: linux-2.4-xfs build broken, Aaron Lehmann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |