Leaving aside the "why didn't I have the tools?" which is probably "they are
included in the image I had been using, but not the release and this has
nothing to do with doing the zypper si".
I still have the following bad exit status:
#zypper si kernel-adaptation-intel-automotive
#cd ~/rpmbuild/SPEC
#rpmbuild -bp kernel-adaptation-intel-automotive.spec
<lots and lots of print statements>
++ cat .config
++ grep -c CONFIG_ARM=y
+ '[' 0 -eq 1 ']'
+ echo Doing kernel-adaptation-intel-automotive.config
Doing kernel-adaptation-intel-automotive.config
+ make ARCH=x86 listnewconfig
error: Bad exit status from /var/tmp/rpm-tmp.Lcu21t (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.Lcu21t (%prep)
-----Original Message-----
From: Kok, Auke-jan H [mailto:[email protected]]
Sent: Friday, June 17, 2011 8:36 PM
To: Foster, Susan B
Cc: [email protected]
Subject: Re: [MeeGo-dev] Errors doing rpmbuild with
kernel-adaptation-intel-automotive
On Fri, Jun 17, 2011 at 5:35 PM, Foster, Susan B <[email protected]>
wrote:
> Oops, mistake in here sorry - I enabled source in the oss-repo and was doing:
>
> zypper si kernel-adaptation-intel-automotive
>
> Which in the past has installed the all the tools needed to build the kernel,
> not just some of them...
yes, that's quite likely. The idea from `si` is that you get the build
dependencies (headers, libraries).
Getting the tools themselves is not part of that for several reasons.
Mostly because it makes generating packages on the server faster, and that's a
good thing.
There are still the zypper patterns, those will give you all the basic
compilation tools in one command. Check `zypper pt` which one you need/have,
and use `zypper in -t pattern $pattern` to install a whole pattern at once.
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
