All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Robert Budde <robert@projekt131.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Deploy binaries not compiled for target / PACKAGE_STRIP = "no" does not work?
Date: Mon, 20 Feb 2012 12:12:11 +0000	[thread overview]
Message-ID: <3915047.7HeCOYZS0V@helios> (raw)
In-Reply-To: <002c01ccefbf$99ccf580$cd66e080$@projekt131.de>

On Monday 20 February 2012 12:05:48 Robert Budde wrote:
> I am trying to write a recipe for packaging "webmin". 

Ah, well the good news is I did this already :) :

http://git.yoctoproject.org/cgit/cgit.cgi/meta-baryon/tree/recipes-
extended/webmin/

There might be some tweaking required as we turned off a few things and applied 
some minor customisations, but it builds and works.

> The web-interface for
> system administration is written entirely in PERL, therefore it "just" has
> to be copied to the right directory (and some conf-files have to be
> generated). Right now the recipe should download the right archive and copy
> the files to the right directory. As the archive contains precompiled
> binaries the "strip"-operations in do_package() fail!? I tried to get rid of
> it by 'PACKAGE_STRIP = "no"', but that does not work.

To turn off stripping you would do INHIBIT_PACKAGE_STRIP ="1", however for 
something like this where there is nothing architecture-specific you would do 
"inherit allarch" which does this for you among other things. However, the 
precompiled binaries the errors refer to are actually not needed and the 
recipes I link to above just delete them before packaging.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-02-20 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 11:05 Deploy binaries not compiled for target / PACKAGE_STRIP = "no" does not work? Robert Budde
2012-02-20 12:12 ` 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=3915047.7HeCOYZS0V@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=robert@projekt131.de \
    /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.