From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Zhu, Yi" <yi.zhu@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix make kernel rpm bug
Date: Thu, 25 Dec 2003 09:49:37 +0000 [thread overview]
Message-ID: <20031225094937.A11396@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0312251254240.16528-100000@mazda.sh.intel.com>; from yi.zhu@intel.com on Thu, Dec 25, 2003 at 02:58:14PM +0800
On Thu, Dec 25, 2003 at 02:58:14PM +0800, Zhu, Yi wrote:
> On Thu, 25 Dec 2003, Jeff Garzik wrote:
> > hmmm, I don't think $(ARCH) makes the rpm --target strings in all
> > cases..
>
> From rpm man page --target PLATFORM will interpret PLATFORM as
> arch-vendor-os and set %_target, %_target_cpu, %_target_os accordingly.
> In this case only arch is set, so vendor and os will remain as default.
>
> If you still think it is too implicit, how about change as below? In case
> you want set RPM_VENDOR_OS to something like "-unknown-linux".
What Jeff means is that $(ARCH) may not be what rpm calls the
architecture. For instance, the kernel has "arm" but RPM has
"armv3l" "armv4l" etc, but doesn't know what "arm" is.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-12-25 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ACA40606221794F80A5670F0AF15F840254C76E@PDSMSX403.ccr.corp.intel.com>
2003-12-25 6:58 ` [PATCH] fix make kernel rpm bug Zhu, Yi
2003-12-25 9:49 ` Russell King [this message]
[not found] <3ACA40606221794F80A5670F0AF15F840254C793@PDSMSX403.ccr.corp.intel.com>
2003-12-26 7:26 ` Zhu, Yi
2003-12-10 9:06 Make rpm patch for cross compile 2.6.0-test11 Zhu, Yi
2003-12-25 2:43 ` [PATCH] fix make kernel rpm bug Zhu, Yi
2003-12-25 4:12 ` Jeff Garzik
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=20031225094937.A11396@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.zhu@intel.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