From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] openjade: autoreconf to fix building on newer host systems
Date: Tue, 12 Jun 2012 14:14:09 +0100 [thread overview]
Message-ID: <1339506849.8065.3.camel@ted> (raw)
In-Reply-To: <4FD68BF8.9030607@intel.com>
On Mon, 2012-06-11 at 17:23 -0700, Scott Garman wrote:
> On 06/11/2012 10:34 AM, Flanagan, Elizabeth wrote:
> > On Sat, Jun 2, 2012 at 10:34 AM, Otavio Salvador
> > <otavio@ossystems.com.br> wrote:
> >> When using an update host system the build environment fails to
> >> properly get config.h done. To solve it we update the build system
> >> thought use of autoreconf. The build failure was:
> >>
> >> ,----
> >> | ...
> >> | DssslApp.cxx:117:36: error: 'PACKAGE' was not declared in this scope
> >> | DssslApp.cxx:118:36: error: 'VERSION' was not declared in this scope
> >> | make[2]: *** [DssslApp.lo] Error 1
> >> `----
> >>
> >> Signed-off-by: Otavio Salvador<otavio@ossystems.com.br>
> >> ---
> >
> > Merged into OE-Core
>
> I don't see this commit in oe-core master?
It was not merged and I've now proposed an alternative patch.
Cheers,
Richard
next prev parent reply other threads:[~2012-06-12 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 17:34 [PATCH 0/1] Fix build failure of openjade using newer host Otavio Salvador
2012-06-02 17:34 ` [PATCH 1/1] openjade: autoreconf to fix building on newer host systems Otavio Salvador
2012-06-11 17:34 ` Flanagan, Elizabeth
2012-06-12 0:23 ` Scott Garman
2012-06-12 13:14 ` Richard Purdie [this message]
2012-06-08 10:33 ` [PATCH 0/1] Fix build failure of openjade using newer host Richard Purdie
2012-06-08 11:52 ` Otavio Salvador
2012-06-12 13:13 ` Richard Purdie
2012-06-12 13:16 ` Otavio Salvador
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=1339506849.8065.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox