[From nobody Mon Apr 22 08:17:18 2013
Received: from catv-157-192.tbwil.ch (catv-157-192.tbwil.ch
	[213.196.157.192]) by webmail.thurcom.ch (Horde Framework) with HTTP;
	Sun, 21 Apr 2013 20:01:16 +0200
Message-ID: <20130421200116.146533bojrb0n2p8@webmail.thurcom.ch>
Date: Sun, 21 Apr 2013 20:01:16 +0200
From: christopher.lamb@thurweb.ch
To: devel@lists.sailfishos.org
Subject: Fwd: mb gives error "sb2: Error: Invalid target specified,
	aborting.": Part 2
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_2wof9st688z0"
Content-Transfer-Encoding: 7bit

This message is in MIME format.

--=_2wof9st688z0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi all

a partial answer to my own question:

Having found the source of mb here:
https://github.com/mer-tools/sdk-setup/blob/master/src/mb

I think it is failing at the line:
grep --color=3Dnever BuildRequires "$SPEC" | sed -e '/^#.*$/d' | gawk =20
-F: '{ print $2 }' | tr ',' ' ' | xargs sb2 -t "$TARGET" -m =20
sdk-install -R zypper in rpm-build

Taking that to pieces, it looks like sb2 is being passed the following:
pkgconfig(QtCore) >=3D 4.8.0 from grep et al.

Next I need to read the sb2 script to work out what is going on  / wrong.

Gr=FCsse

Chris


--=_2wof9st688z0
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

[Anhang entfernt: Ehemaliger Anhangstyp: "message/rfc822", Name: "Weitergeleitete Nachricht: mb gives error "sb2: Error: Invalid target specified, aborting.""]
--=_2wof9st688z0--
]