From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: 'pod' problem building openssl 1.0.1g with latest daisy branch
Date: Mon, 28 Jul 2014 11:40:52 +0100 [thread overview]
Message-ID: <53D628B4.9070503@dynamicdevices.co.uk> (raw)
In-Reply-To: <3638255.FXZXZqP4FB@peggleto-mobl5.ger.corp.intel.com>
On 28/07/2014 11:34, Paul Eggleton wrote:
> Hi Alex,
>
> On Monday 28 July 2014 11:19:25 Alex J Lennon wrote:
>> I pulled the latest daisy branch over the weekend and since am having
>> trouble building openssl 1.0.1g.
>>
>> I removed tmp and rebuilt just in case there was some issue there but
>> the problem remains.
>>
>> Conf:
>>
>> BB_VERSION = "1.22.0"
>> BUILD_SYS = "i686-linux"
>> NATIVELSBSTRING = "Ubuntu-14.04"
>> TARGET_SYS = "arm-poky-linux-gnueabi"
>> MACHINE = "imx6qsabresd"
>> DISTRO = "poky"
>> DISTRO_VERSION = "1.6.1"
>> TUNE_FEATURES = "armv7a vfp neon cortexa9"
>> TARGET_FPU = "vfp-neon"
>> meta
>> meta-yocto = "daisy:37532ceb19e08a44ef2a3c86e63ffb60ae8b8f5c"
>> meta-oe
>> meta-efl
>> meta-webserver
>> meta-networking = "daisy:a6dcf6265822ca1484d991d10a3042e04a960cdb"
>> meta-fsl-arm = "master:fc8bcfae0658375b1c241b6b9633b0c2dce6ac88"
>> meta-fsl-arm-extra = "master:9481991ec1f17bb2555a2a32d1680b1f743d7101"
>> meta-fsl-demos = "master:27fdb2f2642ecd55d5633bde880dd4c37acd0d42"
>> meta-mono = "master:74bd3be613ebb980e60e5b98814d4a4bd96a61e0"
>>
>> Layers:
>>
>> ${BSPDIR}/sources/poky.daisy/meta \
>> ${BSPDIR}/sources/poky.daisy/meta-yocto \
>> ${BSPDIR}/sources/meta-openembedded.daisy/meta-oe \
>> ${BSPDIR}/sources/meta-openembedded.daisy/meta-efl \
>> ${BSPDIR}/sources/meta-openembedded.daisy/meta-webserver \
>> ${BSPDIR}/sources/meta-openembedded.daisy/meta-networking \
>> ${BSPDIR}/sources/meta-fsl-arm \
>> ${BSPDIR}/sources/meta-fsl-arm-extra \
>> ${BSPDIR}/sources/meta-fsl-demos \
>> ${BSPDIR}/sources/meta-mono \
>>
>> Failure seems related to corrupt 'pod' files
>>
>> | installing man1/ciphers.1ssl
>> | installing man1/cms.1ssl
>> | cms.pod around line 457: Expected text after =item, not a number
>> | cms.pod around line 461: Expected text after =item, not a number
>> | cms.pod around line 465: Expected text after =item, not a number
>> | cms.pod around line 470: Expected text after =item, not a number
>> | cms.pod around line 474: Expected text after =item, not a number
>> | POD document had syntax errors at /usr/bin/pod2man line 71.
>> | make: *** [install_docs] Error 255
>> | ERROR: oe_runmake failed
>>
>> I see from a little googling that there's recent (-ish) commentary on an
>> issue building these files with perl
>>
>> e.g.
>> http://askubuntu.com/questions/454575/error-255-when-trying-to-install-opens
>> sl-1-0-1g-from-source
>>
>> I see my perl-native is 5.14.3 so not quite the same as the issue in the
>> link above.
>>
>> Can anybody comment on whether this is a known issue or somehow finger
>> trouble on my part?
> So, I think this is an issue with newer host Perl and OpenSSL 1.0.1g. This
> looks like it might be the patch that fixes it:
>
> https://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=23f5908ac753b176af2a0690e0ebb53c95ef192b
>
> If so we can apply this in daisy (master already has 1.0.1h which includes
> this fix.)
I'll give this a quick test then shortly thanks Paul.
In the meantime I can also confirm that running make install_sw instead
of make install works as an interim - albeit inappropriate for Yocto - fix
ref: https://github.com/openssl/openssl/issues/57
Cheers,
Alex
next prev parent reply other threads:[~2014-07-28 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 10:19 'pod' problem building openssl 1.0.1g with latest daisy branch Alex J Lennon
2014-07-28 10:34 ` Paul Eggleton
2014-07-28 10:40 ` Alex J Lennon [this message]
2014-07-28 10:45 ` Paul Eggleton
2014-07-28 11:14 ` Alex J Lennon
2014-07-28 11:17 ` Paul Eggleton
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=53D628B4.9070503@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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 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.