public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob Turk" <r.turk@chello.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux FSCP (Frequently Submitted Compilation Problems)? (was:  Re: Loop.c File !!!!)
Date: Fri, 23 Nov 2001 08:10:14 +0100	[thread overview]
Message-ID: <9tksuh$mlo$1@ncc1701.cistron.net> (raw)
In-Reply-To: LINKIFYCfHAJBIbBGeGfDGFBDDBICcBBJaCabcceCCHDbBdLINKIFYJeHJeBFcCJbAEHIEcHGHGabHJdccAIGGdCFaEHbELINKIFYbEFfdHdHffGDGDbaFDaBeaDHGEdbCHaBBaeAAGCfLINKIFYddJFBcAJebGfFGJAHCAHJdacAfcdFGEAJJbIFcCcLINKIFYHHIcFdAcBCbeJACBJbCIFdccbdIaGCdfbIeAHacALINKIFYaDdaGDBEbbdAGCGdEAecIcfBJIBCBDHdGaFGDHJF <200111230116.fAN1G8p04152@vindaloo.ras.ucalgary.ca>

"Richard Gooch" <rgooch@ras.ucalgary.ca> wrote in message
news:cistron.200111230116.fAN1G8p04152@vindaloo.ras.ucalgary.ca...
> Andreas Dilger writes:
> > On Nov 23, 2001  11:03 +1100, Stuart Young wrote:
> > > >Something along the lines of 'Your kernel failed to build. Check
> > > >www.where-ever-the-buglist-is.org for known issues with your kernel. Post
> > > >your problem on the kernel list if this is not a FRB'. Is this something
> > > >that can be done easily?
> > >
> > > At the bottom of the file, have ANOTHER link to a generic FAQ about
> > > compilation problems (which covers all the major things like forgetting to
> > > install an assembler, the broken old build stuff, 'make dep' before
> > > compiling modules, etc). The FAQ could be on the kernel mirrors as well
> > > (and I don't see why not, as this is all kernel related, and definitely a
> > > resource that needs to be in more than one place).
> >
> > Yes!!!!  Anything to reduce the number of repeat problems reported
> > is good in my books.  It might also hold a pointer to Linus' (or
> > Marcello's) -pre patch area, with a warning that they are not for
> > everyone.
>
> Well, the FAQ is supposed to answer these questions. There's a whole
> section on compile problems. Do we need another FAQ?
>

No, we do not need another FAQ. But we could certainly use a few more *pointers*
to the existing ones.

Rob





  parent reply	other threads:[~2001-11-23  7:14 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
2001-11-23  7:10             ` Rob Turk [this message]
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='9tksuh$mlo$1@ncc1701.cistron.net' \
    --to=r.turk@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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