[prev in list] [next in list] [prev in thread] [next in thread] 

List:       meego-dev
Subject:    Re: [MeeGo-dev] Errors doing rpmbuild
From:       "Clark, Joel" <joel.clark () intel ! com>
Date:       2011-06-23 19:10:59
Message-ID: 667A27282ACF7941B0F557DAD3491E160115862405 () rrsmsx504 ! amr ! corp ! intel ! com
[Download RAW message or body]

We would like to know why this work in April but broke in the final release.  What broke with rpmbuild of the intel-automotive rpm?

regards
Joel


-----Original Message-----
From: meego-dev-bounces@meego.com [mailto:meego-dev-bounces@meego.com] On Behalf Of Kok, Auke-jan H
Sent: Thursday, June 23, 2011 11:00 AM
To: Liu, Bing Wei
Cc: meego-dev@meego.com; meego-kernel@meego.com
Subject: Re: [MeeGo-dev] Errors doing rpmbuild with kernel-adaptation-intel-automotive

please take a look at:

http://wiki.meego.com/Recompile_kernel

and, if this isn't enough information, we should document this page
with more detailed instructions.

Auke



On Thu, Jun 23, 2011 at 6:53 AM, Liu, Bing Wei <bing.wei.liu@intel.com> wrote:
> Can MeeGo kernel gurus help to answer this issue - how to rebuild the MeeGo kernel w/o an OBS account?
> I think it's generic to other kernels in MeeGo.
>
> - Bingwei
>
>
>> -----Original Message-----
>> From: meego-dev-bounces@meego.com [mailto:meego-dev-bounces@meego.com]
>> On Behalf Of Foster, Susan B
>> Sent: Tuesday, June 21, 2011 12:26 AM
>> To: Kok, Auke-jan H
>> Cc: meego-dev@meego.com
>> Subject: Re: [MeeGo-dev] Errors doing rpmbuild with kernel-adaptation-
>> intel-automotive
>>
>> 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:auke-jan.h.kok@intel.com]
>> Sent: Friday, June 17, 2011 8:36 PM
>> To: Foster, Susan B
>> Cc: meego-dev@meego.com
>> Subject: Re: [MeeGo-dev] Errors doing rpmbuild with kernel-adaptation-
>> intel-automotive
>>
>> On Fri, Jun 17, 2011 at 5:35 PM, Foster, Susan B
>> <susan.b.foster@intel.com> 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
>> MeeGo-dev@meego.com
>> http://lists.meego.com/listinfo/meego-dev
>> http://wiki.meego.com/Mailing_list_guidelines
>
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[prev in list] [next in list] [prev in thread] [next in thread]