linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joe Green <jgreen@mvista.com>
To: greyham@research.canon.com.au (Graham Stoney),
	pavel_roskin@geocities.com (Pavel Roskin)
Cc: jason_wohlgemuth@gilbarco.com (Wohlgemuth Jason),
	linuxppc-embedded@lists.linuxppc.org
	('linuxppc-embedded@lists.linuxppc.org')
Subject: Re: Unpacking the mvista kernel RPMs
Date: Mon, 10 Apr 2000 09:18:30 -0700	[thread overview]
Message-ID: <00041010295400.03098@minotaur.mvista.com> (raw)
In-Reply-To: <20000410031456.0B51D3C960@elph.research.canon.com.au>


On Sun, 09 Apr 2000, Graham Stoney wrote:
> Pavel Roskin writes:
> > By the way, I found a newer kernel (March, 23) in
> > ftp://ftp.mvista.com/pub/CDK/updates/1.0/ppc_8xx/SRPMS/
>
> How does one go about unpacking one of these RPMs?
>
> I tried ftp'ing the rpm and going:
> % rpm -i hhl-kernel-2.2.13-7.src.rpm
> % rpm -bp /usr/src/redhat/SPECS/hhl-kernel-2.2.13.spec
> ...
> ccp: configs/%{_hhl_kernel_configs}: No such file or directory
> Bad exit status from /var/tmp/rpm-tmp.689 (%prep)

First of all, if you just want to build a kernel, you can use the
kernel-source RPM rather than the SRPM.  This installs a kernel source
tree that is preconfigured to use the cross-development tools.  You
only need to use the SRPM if you want to rebuild the RPMs.

For rebuilding the RPMs, you need to use the "rpmconfig" support.  I've
been meaning to write a README me about this.  We're defining our RPM
spec files in terms of macros that can be changed for different hosts
and targets, so that we can have a common source base for all.  You'll
have to bear with us a while if you want to work with this architecture
right now, because it's still developing.

To build the 2.2.13-7 kernel RPM, you need to install the
hhl-rpmconfig-0.0.2-1 RPM.  Then you need to configure RPM to include
the correct macro files.  When building on a Hard Hat Linux or Red Hat
Linux system, I do this by creating a .rpmrc file in my home directory
that contains the following:

macrofiles:  /usr/lib/rpm/macros:/opt/hardhat/config/rpm/hosts/i686-pc-linux-gnu:/opt/hardhat/config/rpm/targets/%{_target}:~/.rpmmacros

That should all be one line; not sure how it will come out in email.

The /opt/hardhat/config/rpm/hosts/i686-pc-linux-gnu macro file will
provide host-specific macros.  The
/opt/hardhat/config/rpm/targets/%{_target} specification will select a
target macro file based on the target specified when invoking rpm.  For
the 8xx target, we use the rpm option "--target ppc_8xx-hardhat-linux".

I hope this helps.

--
Joe Green <jgreen@mvista.com>
MontaVista Software, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-04-10 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-07 13:54 Software Emulation Exception Wohlgemuth, Jason
2000-04-07 15:20 ` Pavel Roskin
2000-04-07 15:44   ` Dan Malek
2000-04-10  9:37     ` Marcus Sundberg
2000-04-10 16:26       ` Dan Malek
2000-04-11  2:36         ` Jeff Millar
2000-04-11  2:03           ` Dan Malek
2000-04-11  8:50         ` Marcus Sundberg
2000-04-11 12:08           ` Dan Malek
2000-04-11 14:51             ` Marcus Sundberg
2000-04-10  3:14   ` Unpacking the mvista kernel RPMs Graham Stoney
2000-04-10  3:25     ` Jason Wohlgemuth
2000-04-10  4:50       ` Graham Stoney
2000-04-10 17:47         ` Pavel Roskin
2000-04-10 16:18     ` Joe Green [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=00041010295400.03098@minotaur.mvista.com \
    --to=jgreen@mvista.com \
    --cc=greyham@research.canon.com.au \
    --cc=jason_wohlgemuth@gilbarco.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pavel_roskin@geocities.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;
as well as URLs for NNTP newsgroup(s).