[SailfishDevel] Fwd: Fwd: mb gives error "sb2: Error: Invalid target specified, aborting.": Part 3
David Greaves
david.greaves at jollamobile.com
Mon Apr 22 21:06:50 UTC 2013
On 22/04/13 21:46, christopher.lamb at thurweb.ch wrote:
> Hi David
>
> thanks for your stoic patience: unfortunately that did not work either ...
No problem - cc'ing the list for others who may be following.
> To the basics - my host is OSX (but I get the same results on a Win 7 machine)
Always good to know and sensible to report. Hopefully not an issue in this case.
> With yet another new project - Demo4, with the only changes being those that you
> suggest to the .yarl file.
>
> No attempt to build from Qt Creator
>
> Logging on to the SDK as mersdk:
>
> Here is a copy of my shell:
Looks 100% correct
...
> run rpmbuild
> error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo4.tar.bz2
Try this:
grep mersdk /etc/passwd >> /srv/mer/targets/SailfishOS-i486-x86/etc/passwd
and try the mb command again:
mb build -t SailfishOS-i486-x86 rpm/Demo4.spec
Sorry I can't test this properly as I'm rebuilding my QA machine tonight - I
just panicked because I thought I'd lost my OS-X partition! Luckily not :)
David
> As I am connected with mersdk, and mersdk is the owner and group I am more than
> a little lost as to what is wrong ...
It's a little complicated but not rocket science :)
Your build is happening on a virtual machine which is the build-engine - you
know this part. The build engine contains the development tools and compilers etc.
However, inside that build engine are what we call 'targets'. A target is a
very, very light almost-VM. We will have targets for the emulator and for
different devices (including ARM ones). It is the passwd file inside the
*target* that does not understand the username.
It's an annoying one - happily I think I fixed it this weekend.
>
> Chris
>
>
>
> Zitat von "David Greaves" <david.greaves at jollamobile.com>:
>
>> On 22/04/13 20:18, christopher.lamb at thurweb.ch wrote:
>>> Hi David
>>>
>>> I am a microstep further ...8-)
>>>
>>> logged as mersdk, and with a freshly backed Demo3 project I now get this far:
>>>
>>> Building rpm/Demo3.spec for SailfishOS-i486-x86
>>> Checking dependencies...
>>> Loading repository data...
>>> Reading installed packages...
>>> 'pkgconfig(QtCore)>=4.8.0' not found in package names. Trying capabilities.
>>
>> That confused me too.
>>
>> Rather unhelpfully it does *not* say "never mind, found pkgconfig(QtCore)>=4.8.0
>> in capabilities; all is well" :)
>>
>> As a test, I changed it to 4.9.0 and got:
>>
>> 'pkgconfig(QtCore)>=4.9.0' not found in package names. Trying capabilities.
>> No provider of 'pkgconfig(QtCore) >= 4.9.0' found.
>>
>> So that's what it would say if it had a problem.
>>
>>> error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo3.tar.bz2
>>
>> Lets try cleaning up:
>>
>> cd <your app dir>
>>
>> Then:
>>
>> rm -rf /home/mersdk/rpmbuild/*
>> sudo chown -R mersdk:mersdk .
>>
>> And build:
>>
>> mb build -t SailfishOS-i486-x86 rpm/Demo3.spec
>>
>> David
>>
>>
>
>
More information about the Devel
mailing list