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... -----Original Message----- From: Kok, Auke-jan H [mailto:[email protected]] Sent: Friday, June 17, 2011 5:28 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:12 PM, Foster, Susan B <[email protected]> wrote: > Hi, > > I have built kernels on target in the past with MeeGo 1.0 and 1.1, but I am > encountering some issues with the MeeGo 1.2.0 release for IVI. I am > basically following the instructions that OKI-Semi has on Sourceforge - they > have worked flawlessly on MeeGo 1.0 and 1.1. > > I am doing the build on target - both a Crossville-OKI and on one of > the ML7213 reference boards with the same results > > 1) When I do a zypper install kernel-adaptation-intel-automotive I have in > the past gotten all the tools that I need to build a kernel. that doesn't make any sense, this command "just adds a kernel" to your /boot. It won't install any build tools at all, and never has. > With MeeGo 1.2.0 I am having to install rpm-build, ncurses-devel and gcc, >they don't get installed with the kernel, although make and other tools do. > > 2) When I get rpmbuild and gcc and do a #rpmbuild -bp > kernel-adaptation-intel-automotive.spec > > I get the following errors: > > ++ 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) > > I realize that building on the target is about the slowest way of doing this, > and if there is a link to good instructions on setting up a Linux development > machine to do the kernel build, I'm all for that. Get an OBS account on build.meego.com (by filing a bug on bugs.meego.com for access) and you will have the opportunity to let the build server compile your kernels for you, which is by far the easiest method. The obs client can then download what the server compiles ( `osc getbinaries` ) and then you can just rpm install the downloaded rpms right there. All working on a meego system without making it sweat :). There is also some scattered documentation on the wiki if you want to build yourself, but, I really recommend looking into using the meego OBS first. Auke _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
