From: Keith Holman <Keith.Holman@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH 1/5] protobuf: update google protocol buffers to 2.5.0
Date: Fri, 22 Aug 2014 14:56:34 -0400 [thread overview]
Message-ID: <53F79262.80000@windriver.com> (raw)
In-Reply-To: <CADkTA4N6+5NQs=mUQK+CB-vuCmvezHO1vdcZ_6Ob4xr00qyOUA@mail.gmail.com>
On 22/08/14 02:52 PM, Bruce Ashfield wrote:
> Keith,
>
> My build test is showing this:
>
> NOTE: Executing RunQueue Tasks
> ERROR: Function failed: do_compile_ptest_base (log file is located at
> /home/bruce/poky/build/tmp/work/core2-64-poky-linux/protobuf/2.5.0-r0/temp/log.do_compile_ptest_base.30471)
> ERROR: Logfile of failure stored in:
> /home/bruce/poky/build/tmp/work/core2-64-poky-linux/protobuf/2.5.0-r0/temp/log.do_compile_ptest_base.30471
> Log data follows:
> | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
> 'bit-64', 'x86_64-linux', 'common']
> | DEBUG: Executing shell function do_compile_ptest_base
> | cp: cannot stat
> '/home/bruce/poky/build/tmp/work/core2-64-poky-linux/protobuf/2.5.0-r0/protobuf-2.5.0/protobuf.pc':
> No such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile_ptest_base (log file is located
> at /home/bruce/poky/build/tmp/work/core2-64-poky-linux/protobuf/2.5.0-r0/temp/log.do_compile_ptest_base.30471)
> ERROR: Task 9 (/home/bruce/poky/meta-virtualization/recipes-containers/criu/protobuf_2.5.0.bb,
> do_compile_ptest_base) failed with exit code '1'
>
> Does that look familiar ?
No, I never got that. The "protobuf.pc" file should be generated from
the do_compile() command. I wouldn't know why it doesn't generate the
file. Its required to be used by the pkgcfg command in the Makefile in
the examples directory. It contains the location of the compiler flags
and library flags for the compiler being used on the system. The script
makes a temporary copy of this file into the "examples" directory and
modifies it to cross-compile the examples for the target machine.
- Keith
>
> Bruce
>
>
> On Wed, Aug 20, 2014 at 4:46 PM, Keith Holman
> <Keith.Holman@windriver.com> wrote:
>> Upgrade Google Protocol Buffers to version 2.5.0. The previous
>> version 2.4.1 is getting quite old (released April 2011). The newer
>> version provides bug fixes and more functionality. This version adds
>> some speed optimization and the ability to allow multiple enum
>> symbols to have the same value.
>>
>> Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
>> ---
>> recipes-containers/criu/protobuf_2.4.1.bb | 18 ------------------
>> recipes-containers/criu/protobuf_2.5.0.bb | 20 ++++++++++++++++++++
>> 2 files changed, 20 insertions(+), 18 deletions(-)
>> delete mode 100644 recipes-containers/criu/protobuf_2.4.1.bb
>> create mode 100644 recipes-containers/criu/protobuf_2.5.0.bb
>>
>> diff --git a/recipes-containers/criu/protobuf_2.4.1.bb b/recipes-containers/criu/protobuf_2.4.1.bb
>> deleted file mode 100644
>> index d8f1b53..0000000
>> --- a/recipes-containers/criu/protobuf_2.4.1.bb
>> +++ /dev/null
>> @@ -1,18 +0,0 @@
>> -SUMMARY = "protobuf"
>> -DESCRIPTION = "Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats."
>> -HOMEPAGE = "http://code.google.com/p/protobuf/"
>> -SECTION = "console/tools"
>> -LICENSE = "BSD-3-Clause"
>> -
>> -LIC_FILES_CHKSUM = "file://COPYING.txt;md5=af6809583bfde9a31595a58bb4a24514"
>> -
>> -PR = "r0"
>> -
>> -SRC_URI[md5sum] = "dc84e9912ea768baa1976cb7bbcea7b5"
>> -SRC_URI[sha256sum] = "eac6969b617f397247e805267da2b0db3ff9e5a9163b123503a192fbb5776567"
>> -SRC_URI = "http://protobuf.googlecode.com/files/protobuf-${PV}.tar.gz"
>> -
>> -EXTRA_OECONF += " --with-protoc=echo"
>> -inherit autotools
>> -
>> -BBCLASSEXTEND = "native nativesdk"
>> \ No newline at end of file
>> diff --git a/recipes-containers/criu/protobuf_2.5.0.bb b/recipes-containers/criu/protobuf_2.5.0.bb
>> new file mode 100644
>> index 0000000..4a90b2c
>> --- /dev/null
>> +++ b/recipes-containers/criu/protobuf_2.5.0.bb
>> @@ -0,0 +1,20 @@
>> +SUMMARY = "protobuf"
>> +DESCRIPTION = "Protocol Buffers are a way of encoding structured data in \
>> +an efficient yet extensible format. Google uses Protocol Buffers for \
>> +almost all of its internal RPC protocols and file formats."
>> +HOMEPAGE = "http://code.google.com/p/protobuf/"
>> +SECTION = "console/tools"
>> +LICENSE = "BSD-3-Clause"
>> +
>> +LIC_FILES_CHKSUM = "file://COPYING.txt;md5=af6809583bfde9a31595a58bb4a24514"
>> +
>> +PR = "r0"
>> +
>> +SRC_URI[md5sum] = "b751f772bdeb2812a2a8e7202bf1dae8"
>> +SRC_URI[sha256sum] = "c55aa3dc538e6fd5eaf732f4eb6b98bdcb7cedb5b91d3b5bdcf29c98c293f58e"
>> +SRC_URI = "http://protobuf.googlecode.com/files/protobuf-${PV}.tar.gz"
>> +
>> +EXTRA_OECONF += " --with-protoc=echo"
>> +inherit autotools
>> +
>> +BBCLASSEXTEND = "native nativesdk"
>> --
>> 1.9.3
>>
>> --
>> _______________________________________________
>> meta-virtualization mailing list
>> meta-virtualization@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>
next prev parent reply other threads:[~2014-08-22 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 20:46 [PATCH 1/5] protobuf: update google protocol buffers to 2.5.0 Keith Holman
2014-08-20 20:46 ` [PATCH 2/5] protobuf: add python support Keith Holman
2014-08-20 20:46 ` [PATCH 3/5] protobuf: replace spaces with tabs in recipe Keith Holman
2014-08-20 20:46 ` [PATCH 4/5] protobuf: add examples when test feature enabled Keith Holman
2014-08-20 20:46 ` [PATCH 5/5] protobuf: add native package to solve self-dependency Keith Holman
2014-08-22 18:52 ` [PATCH 1/5] protobuf: update google protocol buffers to 2.5.0 Bruce Ashfield
2014-08-22 18:56 ` Keith Holman [this message]
2014-08-22 19:29 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F79262.80000@windriver.com \
--to=keith.holman@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.