createrepo probably makes use of rpm api and extract the rpm header information
and dump it into metadata file.
ThanksAmitesh
From: amitesh.si...@outlook.com
To: pasi.savanai...@reaktor.fi
Date: Fri, 3 May 2013 16:06:52 +0530
CC: general@lists.tizen.org; i...@lists.tizen.org
Subject: Re: [IVI] [Tizen General] How to build a 'not yet supported' arch with
gbs?
Hi Pasi,
I have added 'myarch' into SUPPORTEDARCHS, QEMU_CAN_BUILD and
CHANGE_PERSONALITY. Yes you are right that I need to have compilers and libcs
and others required packages for 'myarch' arch.
For the testing purpose, I have copied all the RPMS of tizen_repo/base/i586/*
to tizen_repo/base/myarch/.
I do modified the tizen.conf file and added following lines. ExportFilter:
\.armv7nh*\.rpm$ armv8el ExportFilter: \.x86_64\.rpm$ x86_64 ExportFilter:
\.i586\.rpm$ i586+ExportFilter: \.i586\.rpm$ myarch ExportFilter:
\.armv5el\.rpm$ armv5el ExportFilter: \.armv5tel\.rpm$ armv5el ExportFilter:
\.armv6el\.rpm$ armv6el
I still get the dependencies error. Any help?
mylib$ gbs build -A myarch -D /var/tmp/ami-gbs/tizen_test.confinfo: generate
repositories ...info: start building packages from: /home/ami/tizen/tizen/mylib
(git)info: prepare sources...info: retrieving repo metadata...info: parsing
package data...info: building repo metadata ...info: package dependency
resolving ...error: *** Error Summary ***=== the following packages failed to
build due to missing build dependencies ===mylib: nothing provides
libc.so.6(GLIBC_2.3) needed by rpm nothing provides libpthread.so.0 needed by
rpm nothing provides libdl.so.2 needed by rpm nothing provides
libpthread.so.0(GLIBC_2.0) needed by rpm.......
--Amitesh
> Subject: Re: [IVI] [Tizen General] How to build a 'not yet supported' arch
> with gbs?
> From: pasi.savanai...@reaktor.fi
> Date: Fri, 3 May 2013 13:21:48 +0300
> CC: general@lists.tizen.org; i...@lists.tizen.org
> To: amitesh.si...@outlook.com
>
> Hi Amitesh,
>
> /usr/lib/python2.7/dist-packages/gitbuildsys/cmd_build.py implements 'gbs
> build' command.
> The snippet shows that supported <archs> are hardcoded into the tool.
> If you need a support for your <arch> you have to implement a support into
> the tool.
> It is not enough to add your arch to the list. You need compilers, libc and
> so on.
>
> --- cmd_build.py ---
>
> SUPPORTEDARCHS = [
> 'x86_64',
> 'i586',
> 'armv6l',
> 'armv7hl',
> 'armv7l',
> ]
>
> # These two dicts maping come from osc/build.py
> CAN_ALSO_BUILD = {
> 'armv7l' :['armv4l', 'armv5l', 'armv6l', 'armv7l', 'armv5el',
> 'armv6el', 'armv7el'],
> 'armv7el':['armv4l', 'armv5l', 'armv6l', 'armv7l', 'armv5el',
> 'armv6el', 'armv7el'],
> 'armv8l' :['armv4l', 'armv5el', 'armv6el', 'armv7el', 'armv8el'
> ],
> 'i586' :['i586', 'i386'],
> 'i686' :['i686', 'i586', 'i386',],
> 'x86_64' :['x86_64', 'i686', 'i586', 'i386'],
> }
>
> QEMU_CAN_BUILD = ['armv4l', 'armv5el', 'armv5l', 'armv6l', 'armv7l',
> 'armv6el', 'armv7el', 'armv7hl', 'armv8el', 'sh4', 'mips',
> 'mipsel', 'ppc', 'ppc64', 's390', 's390x', 'sparc64v',
> 'sparcv9v', 'sparcv9', 'sparcv8', 'sparc', 'hppa'
> ]
>
> ……….
>
> Br,
> Pasi
>
> On May 3, 2013, at 9:57 AM, Amitesh Singh <amitesh.si...@outlook.com> wrote:
>
> > Hi Li,
> >
> > Thanks for the reply. I have created myarch in .../base/ folder and run
> > "createrepo ." but gbs still throws error that myarch is not supported.
> > I dig more into gbs code and it has a check for supported archs which is
> > defined in "/usr/lib/python2.7/dist-packages/gitbuildsys/cmd_build.py"
> > (variable name: SUPPORTEDARCHS). I added 'myarch' there and at some places
> > as well.
> >
> >
> > gbs -v build -A myarch -D /var/tmp/ami-gbs/tizen2.0.conf
> > info: generate repositories ...
> > debug: running command: linux32 depanneur --arch=myarch
> > --repository=/home/ami/tizen_repo/base/
> > --repository=/home/ami/tizen_repo/ivi/ --dist=tizen2.0
> > --configdir=/var/tmp/ami-gbs --path=/home/ami/tizen/tizen/tools/depanneur
> > --threads=1 --packaging-dir=packaging --upstream-branch=upstream
> > error: myarch not support
> > error: Traceback (most recent call last):
> > File "/usr/bin/gbs", line 519, in <module>
> > sys.exit(main(sys.argv))
> > File "/usr/bin/gbs", line 513, in main
> > return module.main(args)
> > File "/usr/lib/python2.7/dist-packages/gitbuildsys/cmd_build.py", line
> > 311, in main
> > raise GbsError('rpmbuild fails')
> > GbsError: <gbs>rpmbuild fails
> >
> >
> > My local repo:
> > $:~/tizen_repo/base$ ls
> > i586 i686 myarch noarch repodata
> >
> > Thanks
> > Amitesh
> >
> >
> >
> > From: hao.h...@intel.com
> > To: amitesh.si...@outlook.com; general@lists.tizen.org; i...@lists.tizen.org
> > Subject: RE: [Tizen General] How to build a 'not yet supported' arch with
> > gbs?
> > Date: Fri, 3 May 2013 06:49:15 +0000
> >
> > Supposedly the build arch is decided by repo on ~/.gbs.conf
> > For example,
> > http://download.tizen.org/snapshots/2.0/common/tizen-2.0_20130218.10/repos/base/,
> > it has ia32/i586, armv7l, so it can be built with i586 or armv7l
> >
> > From: general-boun...@lists.tizen.org
> > [mailto:general-boun...@lists.tizen.org] On Behalf Of Amitesh Singh
> > Sent: Friday, May 03, 2013 2:42 PM
> > To: general@lists.tizen.org; i...@lists.tizen.org
> > Subject: [Tizen General] How to build a 'not yet supported' arch with gbs?
> >
> > Hi All,
> >
> > How can I build a custom target arch with gbs? Lets say I want to build a
> > arch name "myarch" with gbs with "gbs buld -A myarch".
> > gbs uses depanneur for package building.
> >
> >
> > Thanks
> > Amitesh
> >
> > _______________________________________________
> > IVI mailing list
> > i...@lists.tizen.org
> > https://lists.tizen.org/listinfo/ivi
>
_______________________________________________
IVI mailing list
i...@lists.tizen.org
https://lists.tizen.org/listinfo/ivi _______________________________________________
General mailing list
General@lists.tizen.org
https://lists.tizen.org/listinfo/general
