=== the following packages failed to build due to rpmbuild issue (3) ===
libexif:
/home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/logs/fail/libexif-0.6.21-1/log.txt
fuse:
/home/marship/GBS-ROOT/local/repos/tizen3.0_common/x86_64/logs/fail/fuse-2.9.6-0/log.txt
iptables:
/home/marship/GBS-ROOT/local/repos/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 <macromars...@gmail.com> 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/logs/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 <macromars...@gmail.com>
> wrote:
>
>> Thanks.
>> I am trying now.
>>
>>
>>
>> On Mon, Oct 24, 2016 at 10:47 AM, Geunsik Lim <lee...@gmail.com> 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/snapshots/tizen/common/latest/buil
>>> ddata/manifest/tizen-common_20161021.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/projects.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
>>> --
>>>
>>
>>
>
_______________________________________________
General mailing list
General@lists.tizen.org
https://lists.tizen.org/listinfo/general
