as in summary. Reproducible: Always Steps to Reproduce: 1. make sure protobuf-3.0.0_beta3 installed 2. emerge criu 3. notice failure 4. emerge -1 =protobuf-3.0.0_beta2 5. emerge criu is successful Actual Results: protobuf-3.0.0-beta-3/src/google/protobuf/compiler/parser.cc:547] No syntax specified for the proto file: core-arm.proto. Please use 'syntax = "proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to proto2 syntax.) protoc-c --proto_path=images/ --c_out=images/ images/stats.proto [libprotobuf WARNING /var/tmp/portage/dev-libs/protobuf-3.0.0_beta3/work/protobuf-3.0.0-beta-3/src/google/protobuf/compiler/parser.cc:547] No syntax specified for the proto file: stats.proto. Please use 'syntax = "proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to proto2 syntax.) make[1]: *** No rule to make target 'images/stats.pb-c.c', needed by 'images/stats.o'. Stop. make[1]: Leaving directory '/var/tmp/portage/sys-process/criu-2.3/work/criu-2.3' Makefile:178: recipe for target 'images/built-in.o' failed make: *** [images/built-in.o] Error 2 [31;01m*[0m ERROR: sys-process/criu-2.3::gentoo failed (compile phase): [31;01m*[0m emake failed [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=sys-process/criu-2.3::gentoo'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=sys-process/criu-2.3::gentoo'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/sys-process/criu-2.3/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-process/criu-2.3/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/sys-process/criu-2.3/work/criu-2.3' [31;01m*[0m S: '/var/tmp/portage/sys-process/criu-2.3/work/criu-2.3
Created attachment 438782 [details] build.log
Affirmative. Same bug here.
Sadly dev-libs/protobuf-3.0.0_beta2 is already removed from tree, so we could only downgrade to protobuf-2.6.1-r3, after masking beta3 manually. This pulls in more dependency's as beta2 and causes some blocks if not using a similar line like this: At my box: emerge -Dav --backtrack=50 =dev-libs/protobuf-2.6.1-r3 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/python-dateutil-2.5.3::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3 -python3_5" 232 KiB [ebuild N ] dev-python/python-gflags-3.0.2::gentoo PYTHON_TARGETS="python2_7 -pypy" 0 KiB [ebuild N ] dev-python/pytz-2016.3::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3 -python3_5" 0 KiB [ebuild N ] dev-python/google-apputils-0.4.2-r1::gentoo USE="{-test}" PYTHON_TARGETS="python2_7" 0 KiB [ebuild r UD ] dev-libs/protobuf-2.6.1-r3:0/9::gentoo [3.0.0_beta3:0/10::gentoo] USE="java python source%* vim-syntax zlib -emacs -examples -static-libs (-test%)" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 (-python3_3%) (-python3_4%*) (-python3_5%)" 0 KiB [uninstall ] dev-java/protobuf-java-3.0.0_beta3:0/10::gentoo USE="source -doc -nano" [blocks b ] <dev-libs/protobuf-3[java(-)] ("<dev-libs/protobuf-3[java(-)]" is blocking dev-java/protobuf-java-3.0.0_beta3) [uninstall ] dev-python/protobuf-python-3.0.0_beta3:0/10::gentoo PYTHON_TARGETS="python2_7 python3_4 -python3_3 -python3_5" [blocks b ] <dev-libs/protobuf-3[python(-)] ("<dev-libs/protobuf-3[python(-)]" is blocking dev-python/protobuf-python-3.0.0_beta3) [ebuild rR ] dev-libs/protobuf-c-1.2.1-r1:0/1.0.0::gentoo USE="-static-libs {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild rR ] media-sound/clementine-1.3.1::gentoo USE="cdda dbus mtp udisks -amazoncloud -box -debug -dropbox -googledrive -ipod -lastfm -mms -moodbar -projectm -pulseaudio -skydrive {-test} -vkontakte -wiimote" LINGUAS="de -af -ar -be -bg -bn -br -bs -ca -cs -cy -da -el -en_CA -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -he_IL -hi -hr -hu -hy -ia -id -is -it -ja -ka -kk -ko -lt -lv -mr -ms -my -nb -nl -oc -pa -pl -pt -pt_BR -ro -ru -si_LK -sk -sl -sr -sr@latin -sv -te -tr -tr_TR -uk -uz -vi -zh_CN -zh_TW" 0 KiB Total: 7 packages (1 downgrade, 4 new, 2 reinstalls, 2 uninstalls), Size of downloads: 232 KiB Conflict: 2 blocks The following packages are causing rebuilds: (dev-libs/protobuf-2.6.1-r3:0/9::gentoo, ebuild scheduled for merge) causes rebuilds for: (media-sound/clementine-1.3.1:0/0::gentoo, ebuild scheduled for merge) (dev-libs/protobuf-c-1.2.1-r1:0/1.0.0::gentoo, ebuild scheduled for merge)
Same problem here.
> No syntax specified for the proto file: *.proto Is that the actual cause of this? I would assume that "No rule to make target 'images/stats.pb-c.c', needed by 'images/stats.o'. Stop." is the actual error and the others are just warnings.
I found something else, which does not appear in build.log: *** stack smashing detected ***: protoc-c terminated dmesg logs: [ 2366.200126] protoc-c[3426]: segfault at 2 ip 00007ff9f202d623 sp 00007ffdeadf1de0 error 4 in libgcc_s.so.1[7ff9f201f000+15000]
Duplicate of bug #586972
Hi! > I would assume that "No rule to make > target 'images/stats.pb-c.c', needed by 'images/stats.o'. Stop." is the > actual error and the others are just warnings. Agreed, adjusted bug subject accordingly. If I am not mistaken, the issue is proto-c 3.x crashing on some of CRIU's .proto files: # ebuild criu-2.3.ebuild clean prepare # cd /var/tmp/portage/sys-process/criu-2.3/work/criu-2.3/ # protoc-c --proto_path=images/ --c_out=images/ images/stats.proto 2>/dev/null Segmentation fault That's why there is no images/stats.pb-c.c, after.
I have reported the bug at protobuf upstream now: https://github.com/google/protobuf/issues/1740
(In reply to Sebastian Pipping from comment #9) > If I am not mistaken, the issue is proto-c 3.x crashing on some of CRIU's > .proto files: That's why I think it is a duplicate of bug #586972 (s.a.)
@vapier, tomboy64 Would hard-masking * >=dev-libs/protobuf-3 * dev-python/protobuf-python until upstream has a fix be an option, in your eyes?
I just ran across an issue when building criu, where protoc-c failed to work properly. After rebuilding protobuf-c all was fine. Please test whether recompiling protobuf-c against protobuf-3 solves the problem.
(In reply to M. B. from comment #13) > I just ran across an issue when building criu, where protoc-c failed to work > properly. After rebuilding protobuf-c all was fine. > > Please test whether recompiling protobuf-c against protobuf-3 solves the > problem. Worked here.
Submitted my update/fix as https://github.com/gentoo/gentoo/pull/1816.
Should be fixed via [0]. Please reopen if you run across this issue. [0] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=842bba13133c19720953a8d420400b3de075ec5e
Same here, thanks for the fix!
