mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: William Stearns <wstearns@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CC=kgcc incomplete in 2.4.0-test11-ac1
Date: Tue, 21 Nov 2000 11:11:50 -0500	[thread overview]
Message-ID: <3A1A9EC6.BF0A3C83@didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0011211058200.1207-100000@sparrow.websense.net>

William Stearns wrote:
> 
> Good day, Alan,
>         A kernel build with your latest prepatch still seems to use gcc
> to compile some of the auxiliary tools:
> 
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/mkdep scripts/mkdep.c
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer gentbl.c -o gentbl -lm
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o conmakehash conmakehash.c
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o gen-devlist gen-devlist.c
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build tools/build.c -I/usr/src/linux-2.4.0/include
> 
>         Do any of the above tools need to use kgcc as well, or is gcc
> likely to work just fine?
>         Cheers,
>         - Bill

The userspace tools should be fine with the newer gcc.  It is set up
this way so that the userspace tools use the native compiler when
cross-compiling.  If you're really paranoid, set HOSTCC=kgcc as well.

--

				Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-21 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 16:03 William Stearns
2000-11-21 16:11 ` Brian Gerst [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=3A1A9EC6.BF0A3C83@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wstearns@pobox.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

all inboxes | Powered by JetHome®