public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: guorke <gourke@gmail.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hi,make question
Date: Mon, 20 Jun 2005 12:09:52 +0800	[thread overview]
Message-ID: <d73ab4d00506192109a824926@mail.gmail.com> (raw)
In-Reply-To: <C2515872-AB06-4710-9F90-E8E4AEC1C6F0@mac.com>

Thanks,I got it.
It beacuse  compiler segfaulted.


On 6/20/05, Kyle Moffett <mrmacman_g4@mac.com> wrote:
> On Jun 19, 2005, at 21:44:30, guorke wrote:
> > hi,when complie 2.6.12,i meet the followning message,how to fix it?
> 
> RTFM (Read the f***ing message):
>   When you get an error message, it's usually best to do as it says.
> 
> > ipc/shm.c: In function `shm_inc':
> > ipc/shm.c:99: internal error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
> > make[1]: *** [ipc/shm.o] Error 1
> > make: *** [ipc] Error 2
> 
> Please note where it says: "See <URL> for instructions".  That usually
> means that you should visit the URL and read the instructions contained
> therein.
> 
> Cheers,
> Kyle Moffett
> 
> --
> There are two ways of constructing a software design. One way is to
> make it so simple that there are obviously no deficiencies. And the
> other way is to make it so complicated that there are no obvious
> deficiencies.
>  -- C.A.R. Hoare
> 
>

  reply	other threads:[~2005-06-20  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20  1:44 Hi,make question guorke
2005-06-20  1:51 ` Kyle Moffett
2005-06-20  4:09   ` guorke [this message]
     [not found] ` <200506200618.44344.bonganilinux@mweb.co.za>
2005-06-20  5:31   ` guorke
2005-06-20  7:14     ` Niraj kumar
2005-06-20 17:56       ` Bongani Hlope

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=d73ab4d00506192109a824926@mail.gmail.com \
    --to=gourke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    /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