From: Andrew Jeffery <andrew@aj.id.au> To: Khem Raj <raj.khem@gmail.com> Cc: "openembeded-devel" <openembedded-devel@lists.openembedded.org>, openbmc@lists.ozlabs.org Subject: Re: [oe] [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Date: Fri, 01 Jun 2018 12:06:05 +0930 [thread overview] Message-ID: <1527820565.499695.1392530280.7147CEB3@webmail.messagingengine.com> (raw) In-Reply-To: <CAMKF1spm=GQQq90gu58BdrNtqPQx_fxnA01ar9Jmr4PbQnmttQ@mail.gmail.com> Hi Khem, Thanks for testing. On Fri, 1 Jun 2018, at 02:18, Khem Raj wrote: > fails to build on qemumips > Do I have to support MIPS for the recipe to be acceptable? Is there some way we can limit the recipe to architectures for which the software is known to work? Andrew > | ../../git/src/ptrace.cc: In function 'user_regs_struct > pyflame::PtraceGetRegs(pid_t)': > | ../../git/src/ptrace.cc:125:41: error: return type 'user_regs_struct > {aka struct user_regs_struct}' is incomplete > | user_regs_struct PtraceGetRegs(pid_t pid) { > | ^ > | ../../git/src/ptrace.cc:125:18: error: ambiguating new declaration > of 'void pyflame::PtraceGetRegs(pid_t)' > | user_regs_struct PtraceGetRegs(pid_t pid) { > | ^~~~~~~~~~~~~ > | In file included from ../../git/src/ptrace.cc:15:0: > | ../../git/src/./ptrace.h:48:18: note: old declaration > 'user_regs_struct pyflame::PtraceGetRegs(pid_t)' > | user_regs_struct PtraceGetRegs(pid_t pid); > | ^~~~~~~~~~~~~ > | ../../git/src/ptrace.cc:126:20: error: aggregate 'user_regs_struct > regs' has incomplete type and cannot be defined > | user_regs_struct regs; > | ^~~~ > | ../../git/src/ptrace.cc: In function 'void > pyflame::PtraceSetRegs(pid_t, user_regs_struct)': > | ../../git/src/ptrace.cc:135:48: error: 'regs' has incomplete type > | void PtraceSetRegs(pid_t pid, user_regs_struct regs) { > | ^~~~ > | In file included from ../../git/src/ptrace.cc:15:0: > | ../../git/src/./ptrace.h:29:16: note: forward declaration of > 'user_regs_struct {aka struct user_regs_struct}' > | typedef struct user_regs_struct user_regs_struct; > | ^~~~~~~~~~~~~~~~ > | make[2]: *** [ptrace.o] Error 1 > | make[2]: *** Waiting for unfinished jobs.... > | make[2]: Leaving directory > `/mnt/jenkins/workspace/OpenEmbedded/build/tmp/work/mips32r2-bec-linux/ > python-pyflame/1.6.6-r0/build/src' > > On Tue, May 29, 2018 at 4:48 AM, Andrew Jeffery <andrew@aj.id.au> wrote: > > On Thu, 10 May 2018, at 16:07, Andrew Jeffery wrote: > >> Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > > > > Ping - is there anything I need to revise for this patch or the following two? > > > > Cheers, > > > > Andrew > > > >> --- > >> meta-python/recipes-devtools/python/python-pyflame.inc | 12 ++++++++++++ > >> meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb | 1 + > >> 2 files changed, 13 insertions(+) > >> create mode 100644 meta-python/recipes-devtools/python/python-pyflame.inc > >> create mode 100644 meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> > >> diff --git a/meta-python/recipes-devtools/python/python-pyflame.inc b/ > >> meta-python/recipes-devtools/python/python-pyflame.inc > >> new file mode 100644 > >> index 000000000000..3b84a7e8f8e3 > >> --- /dev/null > >> +++ b/meta-python/recipes-devtools/python/python-pyflame.inc > >> @@ -0,0 +1,12 @@ > >> +SUMMARY = "Pyflame: A Ptracing Profiler For Python" > >> +HOMEPAGE = "https://github.com/uber/pyflame" > >> +SECTION = "devel/python" > >> +LICENSE = "Apache-2.0" > >> +LIC_FILES_CHKSUM = "file://${S}/ > >> LICENSE;md5=2ee41112a44fe7014dce33e26468ba93" > >> +DEPENDS = "python" > >> + > >> +SRC_URI = "git://github.com/uber/pyflame.git;protocol=https;tag=v${PV}" > >> +S = "${WORKDIR}/git" > >> + > >> +inherit pkgconfig autotools > >> + > >> diff --git a/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> b/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> new file mode 100644 > >> index 000000000000..96f03305f883 > >> --- /dev/null > >> +++ b/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> @@ -0,0 +1 @@ > >> +require python-pyflame.inc > >> -- > >> 2.14.1 > >> > > -- > > _______________________________________________ > > Openembedded-devel mailing list > > Openembedded-devel@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jeffery <andrew@aj.id.au> To: Khem Raj <raj.khem@gmail.com> Cc: openbmc@lists.ozlabs.org, openembeded-devel <openembedded-devel@lists.openembedded.org> Subject: Re: [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Date: Fri, 01 Jun 2018 12:06:05 +0930 [thread overview] Message-ID: <1527820565.499695.1392530280.7147CEB3@webmail.messagingengine.com> (raw) In-Reply-To: <CAMKF1spm=GQQq90gu58BdrNtqPQx_fxnA01ar9Jmr4PbQnmttQ@mail.gmail.com> Hi Khem, Thanks for testing. On Fri, 1 Jun 2018, at 02:18, Khem Raj wrote: > fails to build on qemumips > Do I have to support MIPS for the recipe to be acceptable? Is there some way we can limit the recipe to architectures for which the software is known to work? Andrew > | ../../git/src/ptrace.cc: In function 'user_regs_struct > pyflame::PtraceGetRegs(pid_t)': > | ../../git/src/ptrace.cc:125:41: error: return type 'user_regs_struct > {aka struct user_regs_struct}' is incomplete > | user_regs_struct PtraceGetRegs(pid_t pid) { > | ^ > | ../../git/src/ptrace.cc:125:18: error: ambiguating new declaration > of 'void pyflame::PtraceGetRegs(pid_t)' > | user_regs_struct PtraceGetRegs(pid_t pid) { > | ^~~~~~~~~~~~~ > | In file included from ../../git/src/ptrace.cc:15:0: > | ../../git/src/./ptrace.h:48:18: note: old declaration > 'user_regs_struct pyflame::PtraceGetRegs(pid_t)' > | user_regs_struct PtraceGetRegs(pid_t pid); > | ^~~~~~~~~~~~~ > | ../../git/src/ptrace.cc:126:20: error: aggregate 'user_regs_struct > regs' has incomplete type and cannot be defined > | user_regs_struct regs; > | ^~~~ > | ../../git/src/ptrace.cc: In function 'void > pyflame::PtraceSetRegs(pid_t, user_regs_struct)': > | ../../git/src/ptrace.cc:135:48: error: 'regs' has incomplete type > | void PtraceSetRegs(pid_t pid, user_regs_struct regs) { > | ^~~~ > | In file included from ../../git/src/ptrace.cc:15:0: > | ../../git/src/./ptrace.h:29:16: note: forward declaration of > 'user_regs_struct {aka struct user_regs_struct}' > | typedef struct user_regs_struct user_regs_struct; > | ^~~~~~~~~~~~~~~~ > | make[2]: *** [ptrace.o] Error 1 > | make[2]: *** Waiting for unfinished jobs.... > | make[2]: Leaving directory > `/mnt/jenkins/workspace/OpenEmbedded/build/tmp/work/mips32r2-bec-linux/ > python-pyflame/1.6.6-r0/build/src' > > On Tue, May 29, 2018 at 4:48 AM, Andrew Jeffery <andrew@aj.id.au> wrote: > > On Thu, 10 May 2018, at 16:07, Andrew Jeffery wrote: > >> Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > > > > Ping - is there anything I need to revise for this patch or the following two? > > > > Cheers, > > > > Andrew > > > >> --- > >> meta-python/recipes-devtools/python/python-pyflame.inc | 12 ++++++++++++ > >> meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb | 1 + > >> 2 files changed, 13 insertions(+) > >> create mode 100644 meta-python/recipes-devtools/python/python-pyflame.inc > >> create mode 100644 meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> > >> diff --git a/meta-python/recipes-devtools/python/python-pyflame.inc b/ > >> meta-python/recipes-devtools/python/python-pyflame.inc > >> new file mode 100644 > >> index 000000000000..3b84a7e8f8e3 > >> --- /dev/null > >> +++ b/meta-python/recipes-devtools/python/python-pyflame.inc > >> @@ -0,0 +1,12 @@ > >> +SUMMARY = "Pyflame: A Ptracing Profiler For Python" > >> +HOMEPAGE = "https://github.com/uber/pyflame" > >> +SECTION = "devel/python" > >> +LICENSE = "Apache-2.0" > >> +LIC_FILES_CHKSUM = "file://${S}/ > >> LICENSE;md5=2ee41112a44fe7014dce33e26468ba93" > >> +DEPENDS = "python" > >> + > >> +SRC_URI = "git://github.com/uber/pyflame.git;protocol=https;tag=v${PV}" > >> +S = "${WORKDIR}/git" > >> + > >> +inherit pkgconfig autotools > >> + > >> diff --git a/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> b/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> new file mode 100644 > >> index 000000000000..96f03305f883 > >> --- /dev/null > >> +++ b/meta-python/recipes-devtools/python/python-pyflame_1.6.6.bb > >> @@ -0,0 +1 @@ > >> +require python-pyflame.inc > >> -- > >> 2.14.1 > >> > > -- > > _______________________________________________ > > Openembedded-devel mailing list > > Openembedded-devel@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2018-06-01 2:36 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-10 6:37 [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Andrew Jeffery 2018-05-10 6:37 ` Andrew Jeffery 2018-05-10 6:37 ` [meta-python][PATCH v2 2/3] meta-python: Port python-pyflame to 32-bit ARM Andrew Jeffery 2018-05-10 6:37 ` Andrew Jeffery 2018-05-10 6:37 ` [meta-python][PATCH v2 3/3] meta-python: Make python-pyflame cope with prelinked ELFs Andrew Jeffery 2018-05-10 6:37 ` Andrew Jeffery 2018-05-29 11:48 ` [meta-python][PATCH v2 1/3] meta-python: Add python-pyflame recipe Andrew Jeffery 2018-05-29 11:48 ` Andrew Jeffery 2018-05-29 17:04 ` [oe] " Khem Raj 2018-05-29 17:04 ` Khem Raj 2018-05-29 22:03 ` [oe] " Andrew Jeffery 2018-05-29 22:03 ` Andrew Jeffery 2018-05-29 22:23 ` [oe] " Khem Raj 2018-05-29 22:23 ` Khem Raj 2018-05-29 22:29 ` [oe] " Andrew Jeffery 2018-05-29 22:29 ` Andrew Jeffery 2018-05-31 16:48 ` [oe] " Khem Raj 2018-05-31 16:48 ` Khem Raj 2018-06-01 2:36 ` Andrew Jeffery [this message] 2018-06-01 2:36 ` Andrew Jeffery 2018-06-01 4:37 ` [oe] " Khem Raj 2018-06-01 4:37 ` Khem Raj 2018-06-01 5:52 ` [oe] " Andrew Jeffery 2018-06-01 5:52 ` Andrew Jeffery 2018-06-22 21:12 ` [oe] " Khem Raj 2018-06-22 21:12 ` Khem Raj 2018-09-04 9:38 ` [oe] " Martin Jansa 2018-09-04 9:38 ` Martin Jansa 2018-09-04 18:51 ` [oe] " Khem Raj 2018-09-04 18:51 ` Khem Raj 2018-09-10 18:43 ` [meta-python][PATCH] python-pyflame: skip for aarch64 as well Martin Jansa
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=1527820565.499695.1392530280.7147CEB3@webmail.messagingengine.com \ --to=andrew@aj.id.au \ --cc=openbmc@lists.ozlabs.org \ --cc=openembedded-devel@lists.openembedded.org \ --cc=raj.khem@gmail.com \ /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: linkBe 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.