mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: "Rob Turk" <r.turk@chello.nl>
Subject: Re: Linux FSCP (Frequently Submitted Compilation Problems)?  (was:  Re: Loop.c File !!!!)
Date: Fri, 23 Nov 2001 11:03:02 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20011123105317.00a0c940@mail.amc.localnet> (raw)
In-Reply-To: <9ti8e5$9bl$1@ncc1701.cistron.net>
In-Reply-To: <Pine.LNX.4.21.0111202025290.6299-100000@brick> <5.1.0.14.2.20011121082413.00abadd0@pop.gmx.net> <5.1.0.14.0.20011122100929.009ead30@mail.amc.localnet>

At 08:07 AM 22/11/01 +0100, Rob Turk wrote:
>"Stuart Young" <sgy@amc.com.au> wrote:
> > Why not do it like the current Changelog, put it in the kernel
> > repository, and make sure it hits all the mirrors. A little
> > selective advertising (eg: someone mention it on slashdot,
> > newsforge, debianplanet, etc), and people will start using it.
> > Just suffix the file with the version number, just like the
> > Changelog. Because the file will be small, it's possible that some
> > mirrors will get quick updates before they get the kernel itself.
> > This covers all the version specific problems at least.
>
>Most of the people which post without reading previous entries in the 
>newsgroupwill also not read FRB (Frequently Reported Bugs) files. I 
>actually got a greatsuggestion in from Martin Bene. He suggests putting a 
>last line in the build process which always shows up if a failure occurs 
>during kernel compiles.
>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?

That's a good idea, but not mutually exclusive of what I was suggesting.

If fact, the two work quite well together, as the web reference (on failed 
compile) could point to the file I'm suggesting on the kernel mirrors. And 
it's hardly an issue to pull all the version info out of the kernel to 
provide a version number on the end of the file.

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).


AMC Enterprises P/L    - Stuart Young
First Floor            - Network and Systems Admin
3 Chesterville Rd      - sgy@amc.com.au
Cheltenham Vic 3192    - Ph:  (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755


  parent reply	other threads:[~2001-11-23  0:03 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 [this message]
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:40             ` Keith Owens
2001-11-23  4:38           ` Richard Gooch
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=5.1.0.14.0.20011123105317.00a0c940@mail.amc.localnet \
    --to=sgy@amc.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.turk@chello.nl \
    /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

all inboxes | Powered by JetHome®