public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Renato S. Yamane" <renatoyamane@mandic.com.br>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.6.22.5 on Debian Etch (internal compiler error)
Date: Sun, 26 Aug 2007 19:51:51 -0300	[thread overview]
Message-ID: <46D20407.5060804@mandic.com.br> (raw)
In-Reply-To: <9a8748490708261520h74e97bb5sc486b1cf8294c686@mail.gmail.com>

Jesper Juhl escreveu:
> On 27/08/07, Renato S. Yamane <renatoyamane@mandic.com.br> wrote:
>> Can someone help me with this?
>>
>> $ make xconfig
>> HOSTCC  scripts/basic/fixdep
>> scripts/basic/fixdep.c: In function 'parse_dep_file':
>> scripts/basic/fixdep.c:399: internal compiler error: segmentation fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>> For Debian GNU/Linux specific bug reporting instructions,
>> see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
>> Preprocessed source stored into /tmp/ccyzmUDF.out file, please attach
>> this to your bugreport.
>> make[1]: ** [scripts/basic/fixdep] Error 1
>> make: ** [scripts_basic] Error 2
> 
> Is it repeatable or just a one-off?

I can't compile 2.6.22.5 because this error EVER appear.

> I'm using gcc 4.1.2 as well :
> 
> $ gcc --version
> gcc (GCC) 4.1.2

$ gcc --version
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)

I think that is missing some dependency, but build-essential package is 
installed.

Regards,
Renato

  reply	other threads:[~2007-08-26 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 22:10 Compiling 2.6.22.5 on Debian Etch (internal compiler error) Renato S. Yamane
2007-08-26 22:20 ` Jesper Juhl
2007-08-26 22:51   ` Renato S. Yamane [this message]
2007-08-27 13:16 ` Renato S. Yamane

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=46D20407.5060804@mandic.com.br \
    --to=renatoyamane@mandic.com.br \
    --cc=jesper.juhl@gmail.com \
    --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