From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: OpenSSL compile failure - building-docs related
Date: Thu, 30 May 2013 13:36:38 +0100 [thread overview]
Message-ID: <51A747D6.6000203@communistcode.co.uk> (raw)
In-Reply-To: <51A7470C.403@communistcode.co.uk>
On 30/05/13 13:33, Jack Mitchell wrote:
> I hit this today after a pull on master, seems to be an issue with perl
> maybe? Anyone have a clue what it might mean? A -c clean didn't fix up
> the issue.
>
> Attached(1)
>
> Cheers,
> Jack.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
Hmmm, seems a discussion here put it down to a dodgy perl, does this
mean that my hosts perl could be trashed?
http://forums.gentoo.org/viewtopic-t-958406.html?sid=008a250955b12c23986955ae9f3dcca0
Cheers,
Jack.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-05-30 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 12:33 OpenSSL compile failure - building-docs related Jack Mitchell
2013-05-30 12:36 ` Jack Mitchell [this message]
2013-05-30 13:37 ` Jonathan Liu
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=51A747D6.6000203@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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