From: Pete Zaitcev <zaitcev@redhat.com>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] small sparc Makefile cleanups
Date: Tue, 26 Aug 2003 21:33:24 -0400 [thread overview]
Message-ID: <20030826213324.B16588@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030826221922.GJ7038@fs.tum.de>; from bunk@fs.tum.de on Wed, Aug 27, 2003 at 12:19:23AM +0200
> -#
> -# Uncomment the first CFLAGS if you are doing kgdb source level
> -# debugging of the kernel to get the proper debugging information.
> -
> -IS_EGCS := $(shell if $(CC) -m32 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo y; else echo n; fi; )
> -NEW_GAS := $(shell if $(LD) --version 2>&1 | grep 'elf64_sparc' > /dev/null; then echo y; else echo n; fi)
Actually, let me rephrase the question. Does anyone still use
UltraPenguin 1.x or Red Hat 5.x userland for kernel hacking?
If I get no reply in a week, this goes in.
-- Pete
prev parent reply other threads:[~2003-08-27 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 22:19 [2.6 patch] small sparc Makefile cleanups Adrian Bunk
2003-08-27 1:30 ` Pete Zaitcev
2003-08-27 1:33 ` Pete Zaitcev [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=20030826213324.B16588@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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