Now I am hanging on build /home/marship/tizen_common/platform/core/appfw/tpk-backend/ it missing cmake, libxml-2. I tried to add opensuse44.2's repo for it then it stop complaining. Now I stop at following which is conflicts, libgdbm exists in prebuilt/x86_64 but is it libgdbm.so.4, which is not 3. And for libsmack.so.1, same in prebuilt/x86_64, same file, but don't know why gbs doesn't detect it. And capi-system-info, not clue how it jump in the building of tpk-backend, I "grep" but can't find any config file contains it. == the following packages failed to build due to missing build dependencies (1) === tpk-backend: nothing provides libgdbm.so.3()(64bit) needed by capi-system-info nothing provides libsmack.so.1(LIBSMACK_1.2)(64bit) needed by libsecurity-manager-client nothing provides libsmack.so.1(LIBSMACK_1.1)(64bit) needed by security-manager
On Thu, Oct 27, 2016 at 3:26 AM, Scott Zhang <[email protected]> wrote: > I have added the remote repo "http://download.tizen.org/ > snapshots/tizen/common/latest/repos/x86_64-wayland/packages/x86_64/" to > .gbs.conf too .Now I compiled few more projects. > But where is cmake? I can't find cmake in project local repo and remote > repo > I have checked the ia32 repo but still see no cmake there. > > if read document the build-root image use zypper, does that mean it can > use openSuse's repos? which version should I use? > > On Thu, Oct 27, 2016 at 2:52 AM, Scott Zhang <[email protected]> > wrote: > >> Is there any other outside repository need to be added into the .gbs.conf? >> Thanks. >> >> >> info: *** Build Status Summary *** >> === the following packages failed to build due to missing build >> dependencies (596) === >> tpk-backend: >> nothing provides boost-devel >> nothing provides cmake >> nothing provides gtest-devel >> nothing provides pkgconfig(app-installers) >> nothing provides pkgconfig(manifest-parser) >> nothing provides pkgconfig(pkgmgr) >> nothing provides pkgconfig(tpk-manifest-handlers) >> capi-content-mime-type: >> nothing provides cmake >> nothing provides pkgconfig(dlog) >> nothing provides pkgconfig(capi-base-common) >> nothing provides pkgconfig(xdgmime) >> >> >> On Thu, Oct 27, 2016 at 1:10 AM, Scott Zhang <[email protected]> >> wrote: >> >>> by manually add " -Wno-maybe-uninitialized" to the CFLAGS in >>> ~/GBS-ROOT/local/sources/tizen3.0_common/iptables-1.4.21-1/iptables.spec, >>> iptables compiled ok. >>> export CFLAGS+=" $RPM_OPT_FLAGS -Wall -Werror -O2 -D_FORTIFY_SOURCE=2 >>> -fno-strict-aliasing -Wno-unused-value -Wno-maybe-uninitialized" >>> >>> Just wander where is the correct file before this iptables.spec was >>> populated. I found another one in >>> "./platform/upstream/iptables/packaging/iptables.spec" >>> but change it doesn't affect the build process. Maybe I should commit it >>> before comiple? >>> >>> >>> On Wed, Oct 26, 2016 at 11:15 PM, Scott Zhang <[email protected]> >>> wrote: >>> >>>> I am familiar with linux and build system, myself a linux driver and >>>> networking application programmer. >>>> If I can disable -Werror=maybe-uninitialized then build iptables can >>>> pass. But my quesiton is, as I am cloning the latest tizen code, all the >>>> projects are supposed to be built successfully by default. >>>> But I get this error, so what's the best/correct way to fix this? >>>> >>>> Yes. I have add Jaehyun Kim into this thread. >>>> >>>> On Wed, Oct 26, 2016 at 10:32 PM, Geunsik Lim <[email protected]> wrote: >>>> >>>>> Please, refer to the https://lists.tizen.org/pi >>>>> permail/general/2016-October/003949.html >>>>> >>>>> BRs, >>>>> Geunsik Lim. >>>>> >>>>> On Wed, Oct 26, 2016 at 10:45 PM, Scott Zhang <[email protected]> >>>>> wrote: >>>>> >>>>>> === the following packages failed to build due to rpmbuild issue (3) >>>>>> === >>>>>> libexif: /home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/lo >>>>>> gs/fail/libexif-0.6.21-1/log.txt >>>>>> fuse: /home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/lo >>>>>> gs/fail/fuse-2.9.6-0/log.txt >>>>>> iptables: /home/marship/GBS-ROOT/local/r >>>>>> epos/tizen3.0_common/x86_64/logs/fail/iptables-1.4.21-1/log.txt >>>>>> === Total succeeded built packages: (136) === >>>>>> >>>>>> How to fix these? >>>>>> >>>>>> On Wed, Oct 26, 2016 at 9:06 PM, Scott Zhang <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> And one more thing, I start use "gbs" to build. >>>>>>> Looks internally, the gbs use "build-root" to build without using my >>>>>>> system's build enviroment. >>>>>>> But I get for example: >>>>>>> warning: build failed, Leaving the logs in >>>>>>> /home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/lo >>>>>>> gs/fail/iptables-1.4.21-1/log.txt >>>>>>> >>>>>>> After open "/fail/iptables-1.4.21-1/log.txt" >>>>>>> >>>>>>> [ 933s] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. >>>>>>> -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT >>>>>>> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL >>>>>>> -I../include -I../include -I/usr/include/uapi -I/usr/include >>>>>>> -I/usr/include/uapi -I/usr/include -Wall -Waggregate-return >>>>>>> -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow >>>>>>> -Wstrict-prototypes -Winline -pipe -O2 -g2 >>>>>>> -feliminate-unused-debug-types >>>>>>> -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector >>>>>>> --param=ssp-buffer-size=32 -Wformat -Wformat-security -fmessage-length=0 >>>>>>> -finline-functions -fdiagnostics-color=never -m64 -march=corei7 >>>>>>> -mtune=corei7-avx -msse4.2 -mfpmath=sse -fasynchronous-unwind-tables >>>>>>> -fno-omit-frame-pointer -g -O2 -g2 -feliminate-unused-debug-types -pipe >>>>>>> -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector >>>>>>> --param=ssp-buffer-size=32 -Wformat -Wformat-security -fmessage-length=0 >>>>>>> -finline-functions -fdiagnostics-color=never -m64 -march=corei7 >>>>>>> -mtune=corei7-avx -msse4.2 -mfpmath=sse -fasynchronous-unwind-tables >>>>>>> -fno-omit-frame-pointer -g -Wall -Werror -O2 -D_FORTIFY_SOURCE=2 >>>>>>> -fno-strict-aliasing -Wno-unused-value -MT libip4tc.lo -MD -MP -MF >>>>>>> .deps/libip4tc.Tpo -c libip4tc.c -fPIC -DPIC -o .libs/libip4tc.o >>>>>>> [ 934s] In file included from libip4tc.c:113:0: >>>>>>> [ 934s] libiptc.c: In function 'iptcc_chain_index_delete_chain': >>>>>>> [ 934s] libiptc.c:623:6: error: 'idx' may be used uninitialized in >>>>>>> this function [-Werror=maybe-uninitialized] >>>>>>> [ 934s] if (idx != idx2) { >>>>>>> [ 934s] ^ >>>>>>> [ 934s] In file included from libip6tc.c:111:0: >>>>>>> [ 934s] libiptc.c: In function 'iptcc_chain_index_delete_chain': >>>>>>> [ 934s] libiptc.c:623:6: error: 'idx' may be used uninitialized in >>>>>>> this function [-Werror=maybe-uninitialized] >>>>>>> [ 934s] if (idx != idx2) { >>>>>>> [ 934s] ^ >>>>>>> [ 934s] cc1: all warnings being treated as errors >>>>>>> [ 934s] Makefile:392: recipe for target 'libip4tc.lo' failed >>>>>>> >>>>>>> >>>>>>> how can I fix this? >>>>>>> thanks >>>>>>> >>>>>>> On Wed, Oct 26, 2016 at 7:19 PM, Scott Zhang <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> Thanks. >>>>>>>> I am trying now. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Oct 24, 2016 at 10:47 AM, Geunsik Lim <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I recommend that you try to use a up-to-date '*.xml' from >>>>>>>>> http://download.tizen.org/snapshots/tizen/common/latest/buil >>>>>>>>> ddata/manifest/ >>>>>>>>> $ curl http://download.tizen.org/snap >>>>>>>>> shots/tizen/common/latest/builddata/manifest/tizen-common_20 >>>>>>>>> 161021.3_arm-wayland.xml > .repo/manifests/common/projects.xml >>>>>>>>> >>>>>>>>> Or, you can fix this issue by modifying incorrect path of the >>>>>>>>> project (e.g. tizen-platform-wrapper) as following after checking a >>>>>>>>> correct >>>>>>>>> path of the project >>>>>>>>> at https://review.tizen.org/gerrit/#/admin/projects/ >>>>>>>>> >>>>>>>>> $ vi .repo/manifests/common/projects.xml >>>>>>>>> * before: >>>>>>>>> <project name="platform/core/appfw/tizen-platform-wrapper" >>>>>>>>> path="platform/core/appfw/tizen-platform-wrapper" >>>>>>>>> revision="e866508e4b35f0fc3b16eb2107dbb3dba42ac23e"/> >>>>>>>>> >>>>>>>>> * after: >>>>>>>>> <project name="platform/core/system/tizen-platform-wrapper" >>>>>>>>> path="platform/core/system/tizen-platform-wrapper" >>>>>>>>> revision="e866508e4b35f0fc3b16eb2107dbb3dba42ac23e"/> >>>>>>>>> >>>>>>>>> >>>>>>>>> * Reference: >>>>>>>>> https://source.tizen.org/documentation/developer-guide/getti >>>>>>>>> ng-started-guide/cloning-tizen-source >>>>>>>>> >>>>>>>>> 2. Replace latest manifest with snapshot manifest and make proper >>>>>>>>> modification by executing one of the following two sets of commands, >>>>>>>>> as >>>>>>>>> appropriate: >>>>>>>>> Tizen Common >>>>>>>>> $ wget <Snapshot_Manifest_URL> -O .repo/manifests/common/project >>>>>>>>> s.xml >>>>>>>>> $ sed -i '3,4d' .repo/manifests/common/projects.xml >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> http://leemgs.fedorapeople.org >>>>>>>>> Don't try to avoid pain if you fail. >>>>>>>>> If you decided to face the challenges in life, >>>>>>>>> you can gain a lot by giving your best. >>>>>>>>> Cheolsang Jeong's Book & life >>>>>>>>> -- >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> http://leemgs.fedorapeople.org >>>>> Don't try to avoid pain if you fail. >>>>> If you decided to face the challenges in life, >>>>> you can gain a lot by giving your best. >>>>> Cheolsang Jeong's Book & life >>>>> -- >>>>> >>>> >>>> >>> >> >
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
