Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: YAPQ: OE recipe for Perl module Crypt::OpenSSL::X509?
Date: Fri, 25 Nov 2016 05:47:29 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1611250534120.31820@ca624034.mitel.com> (raw)


  (side note: if there's a better place to ask about
finding/tweaking/writing perl modules for an OE image, let me know.
i've almost cleared my list of essential perl recipes, just a couple
more i need pretty badly, so a couple more posts coming.)

  for my qemuppc image, i need a (obviously cross-compiled version of)
Crypt::OpenSSL::X509, which i can see at CPAN:

  https://metacpan.org/pod/Crypt::OpenSSL::X509

which has absolutely no hope of being cross-compiled based on the
boilerplate recipe i threw together:

  $ make libcrypt-openssl-x509-perl
  ... snip ...
  | cc1: error: include location "/usr/include/openssl" is unsafe for
  cross-compilation [-Werror=poison-system-directories]
  | cc1: all warnings being treated as errors
  | Makefile:346: recipe for target 'X509.o' failed
  | make: *** [X509.o] Error 1
  | ERROR: oe_runmake failed
  ... snip ...

not at all surprising given this in Makefile.PL:

  ... snip ...
  requires_external_cc();
    inc '-I/usr/include/openssl -I/usr/local/include/ssl -I/usr/local/ssl/include';
    libs '-L/usr/lib -L/usr/local/lib -L/usr/local/ssl/lib -lcrypto';
    ... snip ...

so, clearly, i need to hack that source to support cross-compilation;
i guess i can find another module to use as a template and take it
from there, so two questions:

  1) i'm willing to take a stab at rewriting that source to support
     cross-compiling (for the educational experience), any
     recommendation for a well-written reference module to use as a
     starting point?

  2) if someone already *has* such a recipe, hey, i'm more than happy
     to use it, but i'll still take the time to figure out how to
     write things like that properly.

  any assistance gratefully accepted. one more perl question coming
...

rday

p.s. i'm still poring over jens rehsack's guide to cross compiling
perl:

http://www.netbsd.org/~sno/talks/nrpm/Cross-Compiling-For-Perl-Hackers-Handout.pdf

because, you know, copious free time. :-P

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



                 reply	other threads:[~2016-11-25 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1611250534120.31820@ca624034.mitel.com \
    --to=rpjday@crashcourse.ca \
    --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