Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Amy Fong <amy.fong@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-webserver] apache2 multilib issues
Date: Sat, 16 Feb 2013 20:15:56 +0000	[thread overview]
Message-ID: <6456139.EfBreeO2R8@helios> (raw)
In-Reply-To: <20130215185826.GA873@windriver.com>

Hi Amy,

On Friday 15 February 2013 13:58:26 Amy Fong wrote:
> apache2: multilib issues
> 
> Building a multilib version of apache2 results in many packages
> being installed but not packaged, resulting in apache2 being
> unable to run.
> 
> We fix this by modifying the FILES*${PN} to specify BPN instead of PN
> where required. (Also make he required change for CONFFILES_${PN})
> 
> Signed-off-by: Amy Fong <amy.fong@windriver.com>
> --
>  apache2_2.4.2.bb |   26 +++++++++++++-------------
>  1 file changed, 13 insertions(+), 13 deletions(-)
> 
> diff --git a/recipes-httpd/apache2/apache2_2.4.2.bb
> b/recipes-httpd/apache2/apache2_2.4.2.bb index af8c4ca..1ed189b 100644
> --- a/recipes-httpd/apache2/apache2_2.4.2.bb
> +++ b/recipes-httpd/apache2/apache2_2.4.2.bb

This patch is effectively against the danny branch; master has moved on to 
version 2.4.3. I was about to rebase it on top of master and then I noticed 
that there are still some PN references in the value of EXTRA_OECONF that 
might be problematic for the multilib case. This patch will certainly fix the 
warnings, but has it been tested at runtime?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2013-02-16 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 18:58 [PATCH][meta-webserver] apache2 multilib issues Amy Fong
2013-02-16 20:15 ` Paul Eggleton [this message]

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=6456139.EfBreeO2R8@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=amy.fong@windriver.com \
    --cc=openembedded-devel@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