All of lore.kernel.org
 help / color / mirror / Atom feed
From: rgx <rgx@gmx.de>
To: Adrian Bunk <bunk@fs.tum.de>
Subject: Re: kernel 2.4-22 won't compile...
Date: Sun, 30 Nov 2003 13:19:43 +0100	[thread overview]
Message-ID: <200311301319.43509.rgx@gmx.de> (raw)
In-Reply-To: <20031130034050.GN24581@fs.tum.de>

Adrian Bunk schrieb am Sonntag, 30. November 2003 04:40:
> On Wed, Nov 26, 2003 at 05:34:23PM +0100, rgx wrote:
> > hi there,
>
> Hi Ralf,

Hello Adrian :)
> ...
> #
> # Automatically generated by kcmlinuz: don't edit
> #
> ...
>
> <--  snip  -->
>
>
> WTF is kcmlinuz???

It's a GUI for selecting what to include for compiling a kernel that 
integrates in the KDE control center. Like make configmenu (IIRC)
>
>
> I bet your problems will be gone if you run "make oldconfig" before
> "make bzImage"...

I did "make oldconfig", and then I selected my personal hardware.
Nope, it was the gcc that caused the trouble. I found gcc-2.95 on my 
machine, too, and changed the link of /usr/bin/gcc to this version. 
Then the kernel compiled! It was just to large - now I put most drivers 
to modules - mh, and get some other errors, but let this be another 
thread :)

Just have to find out how to pipe stdout and stderr simultanously into 
ONE log file. something like "make bzImage 1&2>logfile"

Thanx for replying
Regards
Ralf
>
> > Thanks for any hints
> > Regards
> > Ralf
>
> cu
> Adrian


      reply	other threads:[~2003-11-30 12:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 16:34 kernel 2.4-22 won't compile rgx
     [not found] ` <1069865010.9694.120.camel@tweedy.ksc.nasa.gov>
2003-11-26 16:49   ` rgx
2003-11-26 18:13     ` Bob Chiodini
2003-11-26 18:35       ` rgx
2003-11-26 19:03         ` Bob Chiodini
2003-11-26 20:40           ` rgx
2003-11-26 20:57           ` rgx
2003-11-26 16:50 ` Bob Chiodini
2003-11-30  3:40 ` Adrian Bunk
2003-11-30 12:19   ` rgx [this message]

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=200311301319.43509.rgx@gmx.de \
    --to=rgx@gmx.de \
    --cc=bunk@fs.tum.de \
    /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.