From: Keith Owens <kaos@ocs.com.au>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Stuart Young <sgy@amc.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!)
Date: Fri, 23 Nov 2001 15:40:09 +1100 [thread overview]
Message-ID: <17638.1006490409@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 22 Nov 2001 21:22:49 PDT." <20011122212249.U1308@lynx.no>
On Thu, 22 Nov 2001 21:22:49 -0700,
Andreas Dilger <adilger@turbolabs.com> wrote:
>Well, you've seen how many times Keith points people to the FAQ on
>module versions, after they post to the list first. You only see
>the FAQ URL at the bottom of the emails if you have previously read
>the mailing list, which most haven't.
kbuild 2.5:
Starting phase 4 (build) for installable
CC drivers/usb/hpusbscsi.o
... gcc error messages ...
make[1]: *** [drivers/usb/hpusbscsi.o] Error 1
Kernel build failed. Please read the FAQ at http://www.tux.org/lkml/ before sending a bug report
make: *** [phase4] Error 1
next prev parent reply other threads:[~2001-11-23 4:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 23:12 Loop.c File !!!! Miguel Maria Godinho de Matos
2001-11-20 20:59 ` Ryan M. McConahy
2001-11-21 1:03 ` J Sloan
2001-11-21 7:28 ` Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!) DevilKin
2001-11-21 8:57 ` Matt Bernstein
2001-11-21 9:10 ` Rob Turk
2001-11-21 23:18 ` Stuart Young
2001-11-22 7:07 ` Rob Turk
2001-11-23 0:03 ` Stuart Young
2001-11-23 1:03 ` Andreas Dilger
2001-11-23 1:16 ` Richard Gooch
2001-11-23 1:20 ` Arnaldo Carvalho de Melo
2001-11-23 1:45 ` Richard Gooch
2001-11-23 4:22 ` Andreas Dilger
2001-11-23 4:38 ` Richard Gooch
2001-11-23 4:40 ` Keith Owens [this message]
2001-11-23 7:10 ` Rob Turk
2001-11-23 20:18 ` Mike Fedyk
2001-11-20 23:19 ` Loop.c File !!!! Chris Wright
2001-11-26 19:58 ` Bill Davidsen
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=17638.1006490409@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=sgy@amc.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.