Could you please attach the exclude file? Which should contains binaries name or package dir name.
Thanks Qiang From: Vikash Kumar [mailto:vikashsuperc...@gmail.com] Sent: Friday, February 22, 2013 2:20 PM To: Zhang, Qiang Z Cc: Wang, Ning W; general@lists.tizen.org Subject: Re: [Tizen General] Tizen build error for armv7l Hello all, As I was told to exclude all the files with '-x86' if I am building the source for armv7l. I tried to use the "--exclude-from-file" with the files containing the rmps of -x86 files. But in the source code I am not able to find any rpm packages, so I put the rpm packages from the repo directory that I downloaded from http://download.tizen.org/releases/daily/2.0alpha/common/latest/ But still I am getting the same error as before. Any suggestion for the exclude option. Am I doing the right step? Thanks, Vikash On Wed, Feb 20, 2013 at 3:38 PM, Zhang, Qiang Z <qiang.z.zh...@intel.com<mailto:qiang.z.zh...@intel.com>> wrote: well, for .gbs.conf is a config file for gbs, including all modules(remotebuild/build/import/export...). build.conf only used for gbs build module. build.conf defined some package list and macros for creating build root env, where rpmbuild is called to build tizen packages. Thanks Qiang From: Vikash Kumar [mailto:vikashsuperc...@gmail.com<mailto:vikashsuperc...@gmail.com>] Sent: Wednesday, February 20, 2013 5:32 PM To: Zhang, Qiang Z Cc: Wang, Ning W; general@lists.tizen.org<mailto:general@lists.tizen.org> Subject: Re: [Tizen General] Tizen build error for armv7l Hello Qiang, Ok, so it means that to build with local repo, i need to specify -D option. And I am getting that error only when I am not using the '-D' option. Well I would like to ask a small question here. What is the difference between ".gbs.conf" and "build.conf" files and in which scenario are they used? I mean during the build process, when are they used? Thanks, Vikash On Wed, Feb 20, 2013 at 2:42 PM, Zhang, Qiang Z <qiang.z.zh...@intel.com<mailto:qiang.z.zh...@intel.com>> wrote: That means you are using local repo, with local repo, you must specify build config with -D option. Not sure why you have error like "warning: Not well formed xml: /var...", are you specify build conf like: -D /var/tmp/vikash-gbs/gbscachexsBnkF/build.xml You 'd better download http://download.tizen.org/releases/daily/2.0alpha/common/latest/builddata/a300db37ca06dc0948bf006eaf2a15fa0481ac5ef64e1a71695bd6b84901f667-build.conf And specify that conf with -D. Thanks Qiang From: Vikash Kumar [mailto:vikashsuperc...@gmail.com<mailto:vikashsuperc...@gmail.com>] Sent: Wednesday, February 20, 2013 5:01 PM To: Zhang, Qiang Z Cc: Wang, Ning W; general@lists.tizen.org<mailto:general@lists.tizen.org> Subject: Re: [Tizen General] Tizen build error for armv7l Hello Wang and Qiang, As you said that if I dont provide the conf file with '-D' option, gbs will fetch the conf file automatically from the remote repo. I want to ask that which remote repo it will check since I am building the code locally on my system. I have downloaded the repos from http://download.tizen.org/releases/daily/2.0alpha/common/latest/ and provided the local path of that repo in ".gbs.conf" file. Thanks, Vikash. On Wed, Feb 20, 2013 at 2:06 PM, Zhang, Qiang Z <qiang.z.zh...@intel.com<mailto:qiang.z.zh...@intel.com>> wrote: It seems that the buil conf in remote repo was broken, could you please show me which remote repo are you using? Btw, you can try to change to another snapshot repo and try again. Thanks Qiang From: general-boun...@lists.tizen.org<mailto:general-boun...@lists.tizen.org> [mailto:general-boun...@lists.tizen.org<mailto:general-boun...@lists.tizen.org>] On Behalf Of Vikash Kumar Sent: Wednesday, February 20, 2013 3:57 PM To: Wang, Ning W Cc: general@lists.tizen.org<mailto:general@lists.tizen.org> Subject: Re: [Tizen General] Tizen build error for armv7l Hello Wang, Thanks for your reply. I would like to ask some questions here. Am i using the right command for Tizen build? Is it really necessary to provide the "-D" option since I am getting the following error when I am not providing the conf file: info: generate repositories ... warning: Not well formed xml: /var/tmp/vikash-gbs/gbscachexsBnkF/build.xml warning: Not well formed xml: /var/tmp/vikash-gbs/gbscachexsBnkF/build.xml warning: Not well formed xml: /var/tmp/vikash-gbs/gbscachexsBnkF/build.xml error: <gbs>failed to get build conf from repos, please use snapshot repo or specify build config using -D option Thanks, Vikash. On Wed, Feb 20, 2013 at 12:28 PM, Wang, Ning W <ning.w.w...@intel.com<mailto:ning.w.w...@intel.com>> wrote: To exclude some packages, you can use --exclude option or --exclude-from-file option. Detailed usage can be find @ https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build. From: general-boun...@lists.tizen.org<mailto:general-boun...@lists.tizen.org> [mailto:general-boun...@lists.tizen.org<mailto:general-boun...@lists.tizen.org>] On Behalf Of Vikash Kumar Sent: Wednesday, February 20, 2013 12:18 PM To: Jan-Simon Möller Cc: general@lists.tizen.org<mailto:general@lists.tizen.org> Subject: Re: [Tizen General] Tizen build error for armv7l Hello JS, Thanks for your reply. And if possible, would you like to tell me how can I ignore the files with "-x86"? Do I need to mention anything with the build command that I am running? Thanks, Vikash. On Wed, Feb 20, 2013 at 1:27 AM, Jan-Simon Möller <dl...@gmx.de<mailto:dl...@gmx.de>> wrote: For armv7l you have to ignore all files with "-x86" in the build. They are not meant to be compiled on armv7l. Just exclude them from the gbs run. Best, JS Am Dienstag, 19. Februar 2013, 16:39:08 schrieb Vikash Kumar: > Hello all, > > > > We are trying to build Tizen 2.0alpha for armv7l architecture. But every > time, we are getting some error and rpmbuild fails to build. We are > building the whole source code locally, the steps and the outputs are > mentioned below: > > > > gbs build -A armvl -R > /local-dir/releases/daily/2.0alpha/common/latest/repos/Tizen-base/armv7l/pac > kages/ -R > /local-dir/releases/daily/2.0alpha/common/latest/repos/Tizen-main/armv7l/pac > kages/ -D /var/tmp/vikash-gbs/tizen2.0.conf > > > > info: generate repositories ... > > info: start building packages from: /opt/bluetooth/Tizen (git) > > info: prepare sources... > > info: start export source from: > /opt/bluetooth/Tizen/adaptation/bluetooth-tools ... > > info: Creating (native) source archive bluetooth-tools-0.2.26.tar.gz from > 'HEAD' > > info: package files have been exported to: > > /home/vikash/GBS-ROOT/local/sources/tizen2.0/bluetooth-tools-0.2.26-1 > > . > > . > > . > > info: start export source from: /opt/bluetooth/Tizen/toolchains/gawk-x86 ... > > error: line 71: Dependency tokens must begin with alpha-numeric, '_' or > '/': BuildRequires: rpm grep tar patchelf sed -rpmlint-Moblin -rpmlint-mini > -post-build-checks > > error: RPM error while parsing spec: can't parse specfile > > > > error: <gbs>Failed to export packaging files from git tree > > info: start export source from: > /opt/bluetooth/Tizen/toolchains/elfutils-libs-x86 ... > > error: line 69: Dependency tokens must begin with alpha-numeric, '_' or > '/': BuildRequires: rpm grep tar patchelf sed -rpmlint-Moblin -rpmlint-mini > -post-build-checks > > error: RPM error while parsing spec: can't parse specfile > > > > error: <gbs>Failed to export packaging files from git tree > > . > > . > > . > > info: retrieving repo metadata... > > info: parsing package data... > > warning: system-plugin-ia-generic: build arch not compatible: i386 i486 > i586 i686 athlon x86_64 > > warning: xorg-x11-drv-intel: build arch not compatible: ia64 x86_64 i386 > i486 i586 i686 athlon > > /home/vikash/GBS-ROOT/local/sources/tizen2.0/glib2-2.32.3-1/glib2.spec: No > such file or directory > > Use of uninitialized value $name in hash element at /usr/bin/depanneur line > 665. > > Use of uninitialized value $name in hash element at /usr/bin/depanneur line > 679. > > warning: acpid: build arch not compatible: ia64 x86_64 i386 i486 i586 i686 > athlon > > warning: cross-armv7nhl-binutils-accel: build arch not compatible: i386 > i486 i586 i686 athlon > > warning: cross-armv7nhl-binutils: build arch not compatible: i386 i486 i586 > i686 athlon > > /home/vikash/GBS-ROOT/local/sources/tizen2.0/procps-3.2.8-15/procps.spec: > No such file or directory > > Use of uninitialized value $name in hash element at /usr/bin/depanneur line > 665. > > Use of uninitialized value $name in hash element at /usr/bin/depanneur line > 679. > > . > > . > > . > > warning: kernel-adaptation-pc: build arch not compatible: i386 i586 i686 > i386 i486 i586 i686 athlon x86_64 > > warning: device-configs: build arch not compatible: i386 i486 i586 i686 > athlon > > warning: mic-bootstrap: build arch not compatible: i586 > > Use of uninitialized value $version in concatenation (.) or string at > /usr/bin/depanneur line 1492. > > Use of uninitialized value $release in concatenation (.) or string at > /usr/bin/depanneur line 1492. > > info: building repo metadata ... > > info: package dependency resolving ... > > /home/vikash/GBS-ROOT/local/sources/tizen2.0/u-boot-1.3.4-1/u-boot.spec: No > such file or directory > > error: *** Error Summary *** > > === the following packages failed to build because export source files to > build environment failed === > > bash-4.1-1 > > elfutils-libelf-x86-MACRO-7 > > make-MACRO-8 > > xz-libs-x86-MACRO-7 > > . > > . > > . > > === the following packages failed to build due to missing build > dependencies === > > > > nothing provides rpm > > nothing provides rpm-libs > > nothing provides setup > > nothing provides filesystem > > . > > . > > . > > error: <gbs>rpmbuild fails > > > > I don't understand, what is going wrong here!!! > > I have also attached the ".gbs.conf" file, in case anyone require it. > > > > Please provide the solution why this problem is coming? > > Thanks in advance, > > > > Vikash. -- Dipl.-Ing. Jan-Simon Möller jansimon.moel...@gmx.de<mailto:jansimon.moel...@gmx.de>
_______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general
