All of lore.kernel.org
 help / color / mirror / Atom feed
* do_cofigure fail
@ 2019-01-09  8:14 Sheldon 13
  2019-01-09 18:05 ` Patrick Venture
  0 siblings, 1 reply; 6+ messages in thread
From: Sheldon 13 @ 2019-01-09  8:14 UTC (permalink / raw)
  To: openbmc

[-- Attachment #1: Type: text/plain, Size: 2586 bytes --]

After I add a new application (such as *sdbus* or* phosphor-fan-presence*)
using DEVTOOL, I build it with BITBAKE, but it always get error like this:
##########################################################
NOTE: Executing RunQueue Tasks
ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed: do_configure
(log file is located at
/home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
ERROR: Logfile of failure stored in:
/home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
Log data follows:
| DEBUG: Executing python function externalsrc_configure_prefunc
############################################################



My recipe file *sdbusplus_git.bb <http://sdbusplus_git.bb>* was
automatically generated by the DEVTOOL command ,it is like this:
##################################################################################################################
# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order to be
fully functional.
# (Feel free to remove these comments when editing.)

# WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best
guesses - it is
# your responsibility to verify that the values are complete and correct.
#
# The following license files were not able to be identified and are
# represented as "Unknown" below, you will need to check them yourself:
#   LICENSE
LICENSE = "Unknown"
LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"

SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"

# Modify these as desired
PV = "1.0+git${SRCPV}"
SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"

S = "${WORKDIR}/git"

# NOTE: the following library dependencies are unknown, ignoring: gtest
gmock
#       (this is based on recipes that have previously been built and
packaged)
DEPENDS = "gtest systemd"

# NOTE: if this software is not capable of being built in a separate build
directory
# from the source, you should replace autotools with autotools-brokensep in
the
# inherit line
inherit pkgconfig pythonnative autotools

# Specify any options you want to pass to the configure script using
EXTRA_OECONF:
EXTRA_OECONF = ""
###############################################################################################################
and I didn't change the recipe and didn't know how to change it. Can you
help me build my project?

[-- Attachment #2: Type: text/html, Size: 3547 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: do_cofigure fail
  2019-01-09  8:14 do_cofigure fail Sheldon 13
@ 2019-01-09 18:05 ` Patrick Venture
  2019-01-09 18:58   ` Benjamin Fair
  0 siblings, 1 reply; 6+ messages in thread
From: Patrick Venture @ 2019-01-09 18:05 UTC (permalink / raw)
  To: Sheldon 13; +Cc: OpenBMC Maillist

On Wed, Jan 9, 2019 at 12:16 AM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>
> After I add a new application (such as sdbus or phosphor-fan-presence) using DEVTOOL, I build it with BITBAKE, but it always get error like this:
> ##########################################################
> NOTE: Executing RunQueue Tasks
> ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
> ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed: do_configure (log file is located at /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
> ERROR: Logfile of failure stored in: /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
> Log data follows:
> | DEBUG: Executing python function externalsrc_configure_prefunc
> ############################################################
>
>
>
> My recipe file sdbusplus_git.bb was automatically generated by the DEVTOOL command ,it is like this:
> ##################################################################################################################
> # Recipe created by recipetool
> # This is the basis of a recipe and may need further editing in order to be fully functional.
> # (Feel free to remove these comments when editing.)
>
> # WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses - it is
> # your responsibility to verify that the values are complete and correct.
> #
> # The following license files were not able to be identified and are
> # represented as "Unknown" below, you will need to check them yourself:
> #   LICENSE
> LICENSE = "Unknown"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
>
> SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"
>
> # Modify these as desired
> PV = "1.0+git${SRCPV}"
> SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"
>
> S = "${WORKDIR}/git"
>
> # NOTE: the following library dependencies are unknown, ignoring: gtest gmock
> #       (this is based on recipes that have previously been built and packaged)
> DEPENDS = "gtest systemd"
>
> # NOTE: if this software is not capable of being built in a separate build directory
> # from the source, you should replace autotools with autotools-brokensep in the
> # inherit line
> inherit pkgconfig pythonnative autotools
>
> # Specify any options you want to pass to the configure script using EXTRA_OECONF:
> EXTRA_OECONF = ""
> ###############################################################################################################
> and I didn't change the recipe and didn't know how to change it. Can you help me build my project?

Can you provide your full steps to reproduce your workspace, such as,
git clone openbmc, git clone sdbusplus, and so on, as I haven't had
issues recently with devtool.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: do_cofigure fail
  2019-01-09 18:05 ` Patrick Venture
@ 2019-01-09 18:58   ` Benjamin Fair
  2019-01-10  1:46     ` Sheldon 13
  0 siblings, 1 reply; 6+ messages in thread
From: Benjamin Fair @ 2019-01-09 18:58 UTC (permalink / raw)
  To: Patrick Venture; +Cc: Sheldon 13, OpenBMC Maillist

On Wed, Jan 9, 2019 at 10:05 AM Patrick Venture <venture@google.com> wrote:
>
> On Wed, Jan 9, 2019 at 12:16 AM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
> >
> > After I add a new application (such as sdbus or phosphor-fan-presence) using DEVTOOL, I build it with BITBAKE, but it always get error like this:

Why are you adding a new recipe for these applications? You should be
able to use the existing recipes that have already been written.

Here's the one for sdbusplus for instance:
https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-extended/sdbusplus/sdbusplus_git.bb

> > ##########################################################
> > NOTE: Executing RunQueue Tasks
> > ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
> > ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed: do_configure (log file is located at /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
> > ERROR: Logfile of failure stored in: /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
> > Log data follows:
> > | DEBUG: Executing python function externalsrc_configure_prefunc
> > ############################################################
> >
> >
> >
> > My recipe file sdbusplus_git.bb was automatically generated by the DEVTOOL command ,it is like this:
> > ##################################################################################################################
> > # Recipe created by recipetool
> > # This is the basis of a recipe and may need further editing in order to be fully functional.
> > # (Feel free to remove these comments when editing.)
> >
> > # WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses - it is
> > # your responsibility to verify that the values are complete and correct.
> > #
> > # The following license files were not able to be identified and are
> > # represented as "Unknown" below, you will need to check them yourself:
> > #   LICENSE
> > LICENSE = "Unknown"
> > LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
> >
> > SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"
> >
> > # Modify these as desired
> > PV = "1.0+git${SRCPV}"
> > SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"
> >
> > S = "${WORKDIR}/git"
> >
> > # NOTE: the following library dependencies are unknown, ignoring: gtest gmock
> > #       (this is based on recipes that have previously been built and packaged)
> > DEPENDS = "gtest systemd"
> >
> > # NOTE: if this software is not capable of being built in a separate build directory
> > # from the source, you should replace autotools with autotools-brokensep in the
> > # inherit line
> > inherit pkgconfig pythonnative autotools
> >
> > # Specify any options you want to pass to the configure script using EXTRA_OECONF:
> > EXTRA_OECONF = ""
> > ###############################################################################################################
> > and I didn't change the recipe and didn't know how to change it. Can you help me build my project?
>
> Can you provide your full steps to reproduce your workspace, such as,
> git clone openbmc, git clone sdbusplus, and so on, as I haven't had
> issues recently with devtool.

Can you also describe what you're trying to accomplish? Feel free to
join the IRC channel #openbmc on freenode.net if that's easier.

Benjamin

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: do_cofigure fail
  2019-01-09 18:58   ` Benjamin Fair
@ 2019-01-10  1:46     ` Sheldon 13
  2019-01-10 16:38       ` Patrick Venture
  0 siblings, 1 reply; 6+ messages in thread
From: Sheldon 13 @ 2019-01-10  1:46 UTC (permalink / raw)
  To: Benjamin Fair; +Cc: Patrick Venture, OpenBMC Maillist

[-- Attachment #1: Type: text/plain, Size: 4411 bytes --]

I am using openbmc-v2.2 and want to add some new features,just for test.
But when I try to add any application, not only sdbus
or phosphor-fan-presence, but all the application I tried have this problem.
Here is my step:
(1)export TEMPLATECONF=meta-ibm/meta-palmetto/conf
(2)openbmc-env
(3)devtool add sdbusplus https://github.com/openbmc/sdbusplus.git
(4) vim openbmc/build/conf/local.conf
     add"IMAGE_INSTALL_append = " welcome" "
(5)bitbake bitbake obmc-phosphor-image

I have change to existing recipes but the problem is as the same.

Benjamin Fair <benjaminfair@google.com> 于2019年1月10日周四 上午2:59写道:

> On Wed, Jan 9, 2019 at 10:05 AM Patrick Venture <venture@google.com>
> wrote:
> >
> > On Wed, Jan 9, 2019 at 12:16 AM Sheldon 13 <tssheldonpotter@gmail.com>
> wrote:
> > >
> > > After I add a new application (such as sdbus or phosphor-fan-presence)
> using DEVTOOL, I build it with BITBAKE, but it always get error like this:
>
> Why are you adding a new recipe for these applications? You should be
> able to use the existing recipes that have already been written.
>
> Here's the one for sdbusplus for instance:
>
> https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-extended/sdbusplus/sdbusplus_git.bb
>
> > > ##########################################################
> > > NOTE: Executing RunQueue Tasks
> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed:
> do_configure (log file is located at
> /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
> > > ERROR: Logfile of failure stored in:
> /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
> > > Log data follows:
> > > | DEBUG: Executing python function externalsrc_configure_prefunc
> > > ############################################################
> > >
> > >
> > >
> > > My recipe file sdbusplus_git.bb was automatically generated by the
> DEVTOOL command ,it is like this:
> > >
> ##################################################################################################################
> > > # Recipe created by recipetool
> > > # This is the basis of a recipe and may need further editing in order
> to be fully functional.
> > > # (Feel free to remove these comments when editing.)
> > >
> > > # WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best
> guesses - it is
> > > # your responsibility to verify that the values are complete and
> correct.
> > > #
> > > # The following license files were not able to be identified and are
> > > # represented as "Unknown" below, you will need to check them yourself:
> > > #   LICENSE
> > > LICENSE = "Unknown"
> > > LIC_FILES_CHKSUM =
> "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
> > >
> > > SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"
> > >
> > > # Modify these as desired
> > > PV = "1.0+git${SRCPV}"
> > > SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"
> > >
> > > S = "${WORKDIR}/git"
> > >
> > > # NOTE: the following library dependencies are unknown, ignoring:
> gtest gmock
> > > #       (this is based on recipes that have previously been built and
> packaged)
> > > DEPENDS = "gtest systemd"
> > >
> > > # NOTE: if this software is not capable of being built in a separate
> build directory
> > > # from the source, you should replace autotools with
> autotools-brokensep in the
> > > # inherit line
> > > inherit pkgconfig pythonnative autotools
> > >
> > > # Specify any options you want to pass to the configure script using
> EXTRA_OECONF:
> > > EXTRA_OECONF = ""
> > >
> ###############################################################################################################
> > > and I didn't change the recipe and didn't know how to change it. Can
> you help me build my project?
> >
> > Can you provide your full steps to reproduce your workspace, such as,
> > git clone openbmc, git clone sdbusplus, and so on, as I haven't had
> > issues recently with devtool.
>
> Can you also describe what you're trying to accomplish? Feel free to
> join the IRC channel #openbmc on freenode.net if that's easier.
>
> Benjamin
>

[-- Attachment #2: Type: text/html, Size: 6052 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: do_cofigure fail
  2019-01-10  1:46     ` Sheldon 13
@ 2019-01-10 16:38       ` Patrick Venture
       [not found]         ` <CAG4=AL_O4MLzMHp+zq6udUang4sXiPr7-Lnr_vEXQcSewGeoyQ@mail.gmail.com>
  0 siblings, 1 reply; 6+ messages in thread
From: Patrick Venture @ 2019-01-10 16:38 UTC (permalink / raw)
  To: Sheldon 13; +Cc: Benjamin Fair, OpenBMC Maillist

On Wed, Jan 9, 2019 at 5:46 PM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>
> I am using openbmc-v2.2 and want to add some new features,just for test. But when I try to add any application, not only sdbus or phosphor-fan-presence, but all the application I tried have this problem.
> Here is my step:
> (1)export TEMPLATECONF=meta-ibm/meta-palmetto/conf
> (2)openbmc-env
> (3)devtool add sdbusplus https://github.com/openbmc/sdbusplus.git
> (4) vim openbmc/build/conf/local.conf
>      add"IMAGE_INSTALL_append = " welcome" "
> (5)bitbake bitbake obmc-phosphor-image
>
> I have change to existing recipes but the problem is as the same.
>
> Benjamin Fair <benjaminfair@google.com> 于2019年1月10日周四 上午2:59写道:
>>
>> On Wed, Jan 9, 2019 at 10:05 AM Patrick Venture <venture@google.com> wrote:
>> >
>> > On Wed, Jan 9, 2019 at 12:16 AM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>> > >
>> > > After I add a new application (such as sdbus or phosphor-fan-presence) using DEVTOOL, I build it with BITBAKE, but it always get error like this:
>>
>> Why are you adding a new recipe for these applications? You should be
>> able to use the existing recipes that have already been written.

^--- per Benjamin, sdbusplus is already a recipe.  If you want to
develop against it use:

devtool modify -n sdbusplus /workspaces/sdbusplus_wip

s.t. sdbusplus_wip is where you've checked out the code you wish to
modify.  That said, v2.2 of openbmc may be too old to work with HEAD
of sdbusplus.


>>
>> Here's the one for sdbusplus for instance:
>> https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-extended/sdbusplus/sdbusplus_git.bb
>>
>> > > ##########################################################
>> > > NOTE: Executing RunQueue Tasks
>> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
>> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed: do_configure (log file is located at /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
>> > > ERROR: Logfile of failure stored in: /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
>> > > Log data follows:
>> > > | DEBUG: Executing python function externalsrc_configure_prefunc
>> > > ############################################################
>> > >
>> > >
>> > >
>> > > My recipe file sdbusplus_git.bb was automatically generated by the DEVTOOL command ,it is like this:
>> > > ##################################################################################################################
>> > > # Recipe created by recipetool
>> > > # This is the basis of a recipe and may need further editing in order to be fully functional.
>> > > # (Feel free to remove these comments when editing.)
>> > >
>> > > # WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses - it is
>> > > # your responsibility to verify that the values are complete and correct.
>> > > #
>> > > # The following license files were not able to be identified and are
>> > > # represented as "Unknown" below, you will need to check them yourself:
>> > > #   LICENSE
>> > > LICENSE = "Unknown"
>> > > LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
>> > >
>> > > SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"
>> > >
>> > > # Modify these as desired
>> > > PV = "1.0+git${SRCPV}"
>> > > SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"
>> > >
>> > > S = "${WORKDIR}/git"
>> > >
>> > > # NOTE: the following library dependencies are unknown, ignoring: gtest gmock
>> > > #       (this is based on recipes that have previously been built and packaged)
>> > > DEPENDS = "gtest systemd"
>> > >
>> > > # NOTE: if this software is not capable of being built in a separate build directory
>> > > # from the source, you should replace autotools with autotools-brokensep in the
>> > > # inherit line
>> > > inherit pkgconfig pythonnative autotools
>> > >
>> > > # Specify any options you want to pass to the configure script using EXTRA_OECONF:
>> > > EXTRA_OECONF = ""
>> > > ###############################################################################################################
>> > > and I didn't change the recipe and didn't know how to change it. Can you help me build my project?
>> >
>> > Can you provide your full steps to reproduce your workspace, such as,
>> > git clone openbmc, git clone sdbusplus, and so on, as I haven't had
>> > issues recently with devtool.
>>
>> Can you also describe what you're trying to accomplish? Feel free to
>> join the IRC channel #openbmc on freenode.net if that's easier.
>>
>> Benjamin

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: do_cofigure fail
       [not found]         ` <CAG4=AL_O4MLzMHp+zq6udUang4sXiPr7-Lnr_vEXQcSewGeoyQ@mail.gmail.com>
@ 2019-01-11 15:05           ` Patrick Venture
  0 siblings, 0 replies; 6+ messages in thread
From: Patrick Venture @ 2019-01-11 15:05 UTC (permalink / raw)
  To: Sheldon 13, OpenBMC Maillist

On Thu, Jan 10, 2019 at 6:16 PM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>
> Sorry,I didn't know the sdbus has already in this project, if that's the case, then I won't do this. But there is phosphor-fan recipe in the project, so do you know how to check the state of fans by it? If I want to update it to the newest  version, called phosphor-fan-presence, I guess, what should I do?

i'm not super familiar with phosphor-fan-presence configuration, but
searching, I found:

https://github.com/openbmc/openbmc/blob/master/meta-ibm/meta-romulus/recipes-phosphor/fans/phosphor-fan-presence-config-native/config.yaml

>
> Thank you!
>
> Patrick Venture <venture@google.com> 于2019年1月11日周五 上午12:38写道:
>>
>> On Wed, Jan 9, 2019 at 5:46 PM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>> >
>> > I am using openbmc-v2.2 and want to add some new features,just for test. But when I try to add any application, not only sdbus or phosphor-fan-presence, but all the application I tried have this problem.
>> > Here is my step:
>> > (1)export TEMPLATECONF=meta-ibm/meta-palmetto/conf
>> > (2)openbmc-env
>> > (3)devtool add sdbusplus https://github.com/openbmc/sdbusplus.git
>> > (4) vim openbmc/build/conf/local.conf
>> >      add"IMAGE_INSTALL_append = " welcome" "
>> > (5)bitbake bitbake obmc-phosphor-image
>> >
>> > I have change to existing recipes but the problem is as the same.
>> >
>> > Benjamin Fair <benjaminfair@google.com> 于2019年1月10日周四 上午2:59写道:
>> >>
>> >> On Wed, Jan 9, 2019 at 10:05 AM Patrick Venture <venture@google.com> wrote:
>> >> >
>> >> > On Wed, Jan 9, 2019 at 12:16 AM Sheldon 13 <tssheldonpotter@gmail.com> wrote:
>> >> > >
>> >> > > After I add a new application (such as sdbus or phosphor-fan-presence) using DEVTOOL, I build it with BITBAKE, but it always get error like this:
>> >>
>> >> Why are you adding a new recipe for these applications? You should be
>> >> able to use the existing recipes that have already been written.
>>
>> ^--- per Benjamin, sdbusplus is already a recipe.  If you want to
>> develop against it use:
>>
>> devtool modify -n sdbusplus /workspaces/sdbusplus_wip
>>
>> s.t. sdbusplus_wip is where you've checked out the code you wish to
>> modify.  That said, v2.2 of openbmc may be too old to work with HEAD
>> of sdbusplus.
>>
>>
>> >>
>> >> Here's the one for sdbusplus for instance:
>> >> https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-extended/sdbusplus/sdbusplus_git.bb
>> >>
>> >> > > ##########################################################
>> >> > > NOTE: Executing RunQueue Tasks
>> >> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: configure failed
>> >> > > ERROR: sdbusplus-1.0+git999-r0 do_configure: Function failed: do_configure (log file is located at /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229)
>> >> > > ERROR: Logfile of failure stored in: /home/sheldon13/dev/openbmc-2.2/build/tmp/work/armv5e-openbmc-linux-gnueabi/sdbusplus/1.0+git999-r0/temp/log.do_configure.114229
>> >> > > Log data follows:
>> >> > > | DEBUG: Executing python function externalsrc_configure_prefunc
>> >> > > ############################################################
>> >> > >
>> >> > >
>> >> > >
>> >> > > My recipe file sdbusplus_git.bb was automatically generated by the DEVTOOL command ,it is like this:
>> >> > > ##################################################################################################################
>> >> > > # Recipe created by recipetool
>> >> > > # This is the basis of a recipe and may need further editing in order to be fully functional.
>> >> > > # (Feel free to remove these comments when editing.)
>> >> > >
>> >> > > # WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses - it is
>> >> > > # your responsibility to verify that the values are complete and correct.
>> >> > > #
>> >> > > # The following license files were not able to be identified and are
>> >> > > # represented as "Unknown" below, you will need to check them yourself:
>> >> > > #   LICENSE
>> >> > > LICENSE = "Unknown"
>> >> > > LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
>> >> > >
>> >> > > SRC_URI = "git://github.com/openbmc/sdbusplus.git;protocol=https"
>> >> > >
>> >> > > # Modify these as desired
>> >> > > PV = "1.0+git${SRCPV}"
>> >> > > SRCREV = "09c981700d7bd98eed54a670e959a424585dcd84"
>> >> > >
>> >> > > S = "${WORKDIR}/git"
>> >> > >
>> >> > > # NOTE: the following library dependencies are unknown, ignoring: gtest gmock
>> >> > > #       (this is based on recipes that have previously been built and packaged)
>> >> > > DEPENDS = "gtest systemd"
>> >> > >
>> >> > > # NOTE: if this software is not capable of being built in a separate build directory
>> >> > > # from the source, you should replace autotools with autotools-brokensep in the
>> >> > > # inherit line
>> >> > > inherit pkgconfig pythonnative autotools
>> >> > >
>> >> > > # Specify any options you want to pass to the configure script using EXTRA_OECONF:
>> >> > > EXTRA_OECONF = ""
>> >> > > ###############################################################################################################
>> >> > > and I didn't change the recipe and didn't know how to change it. Can you help me build my project?
>> >> >
>> >> > Can you provide your full steps to reproduce your workspace, such as,
>> >> > git clone openbmc, git clone sdbusplus, and so on, as I haven't had
>> >> > issues recently with devtool.
>> >>
>> >> Can you also describe what you're trying to accomplish? Feel free to
>> >> join the IRC channel #openbmc on freenode.net if that's easier.
>> >>
>> >> Benjamin

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-01-11 15:06 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-09  8:14 do_cofigure fail Sheldon 13
2019-01-09 18:05 ` Patrick Venture
2019-01-09 18:58   ` Benjamin Fair
2019-01-10  1:46     ` Sheldon 13
2019-01-10 16:38       ` Patrick Venture
     [not found]         ` <CAG4=AL_O4MLzMHp+zq6udUang4sXiPr7-Lnr_vEXQcSewGeoyQ@mail.gmail.com>
2019-01-11 15:05           ` Patrick Venture

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.