All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheldon 13 <tssheldonpotter@gmail.com>
To: Benjamin Fair <benjaminfair@google.com>
Cc: Patrick Venture <venture@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: do_cofigure fail
Date: Thu, 10 Jan 2019 09:46:39 +0800	[thread overview]
Message-ID: <CAG4=AL8xiASCsHJGsQ-w52uPYqvhWtf-Qs1m01rbekbZdsN39g@mail.gmail.com> (raw)
In-Reply-To: <CADKL2t5pdQ5zNEnn4S+Y9nEUR+XMBv5R2DdvoQLXZ4YNrz0dag@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2019-01-10  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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='CAG4=AL8xiASCsHJGsQ-w52uPYqvhWtf-Qs1m01rbekbZdsN39g@mail.gmail.com' \
    --to=tssheldonpotter@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.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: 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.