From: Saul Wold <sgw@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "Belal, Awais" <Awais_Belal@mentor.com>,
"Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>
Subject: Re: Openssl - config file not being pulled in on the install
Date: Wed, 23 Jan 2013 13:31:47 -0800 [thread overview]
Message-ID: <510056C3.6090805@linux.intel.com> (raw)
In-Reply-To: <20130123212632.GC14381@jama.palm1.palmone.com>
On 01/23/2013 01:26 PM, Martin Jansa wrote:
> On Wed, Jan 23, 2013 at 01:17:29PM -0800, Saul Wold wrote:
>> On 01/23/2013 12:10 PM, Belal, Awais wrote:
>>> Hi Guys,
>>>
>>> This probably went un-noticed because I forgot to put a subject the
>>> first time around... my bad!
>>>
>>> I have a question regarding openssl. The openssl.inc file under the poky
>>> package creates a -misc package which is not directly installed unless
>>> either put in RDPENEDS or RRECOMMENDS. This package (-misc) contains the
>>> openssl configuration file which is required while generating
>>> certificates on the target otherwise the command says:
>>> /
>>> WARNING: can't open config file: /usr/lib/ssl/openssl.cnf//
>>> Unable to load config info from /usr/lib/ssl/openssl.cnf//
>>> /
>>>
>>> In an older version of the recipe attached here, the correct method is
>>> being (this is my understanding) to get that file in on the target while
>>> installing.
>>>
>>> Any guidance here would be much appreciated.
>>>
>> Based on reading some of the history and such, I think the best answer
>> would be to move the openssl.cnf file to FILES_${PN} line, since
>> ordering wise it will get pick up that file and it is needed, not
>> recommeded.
>
> Can you please use u-a for that config file if you decide to do it?
>
Excellent suggestion!
probably need to do this with a few more of the config files also!
Sau!
> Some recipes want to provide own openssl.cnf which requires bbappend
> like this one:
> https://github.com/webOS-ports/meta-webos/commit/f2650858ae6f78b016107e622ab7be8a67e954c7
>
> Cheers,
>
>>
>> We would welcome a tested patch.
>>
>> Thanks
>> Sau!
>>
>>> BR,
>>> Awais Belal
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2013-01-23 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:10 Openssl - config file not being pulled in on the install Belal, Awais
2013-01-23 21:17 ` Saul Wold
2013-01-23 21:26 ` Martin Jansa
2013-01-23 21:31 ` Saul Wold [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=510056C3.6090805@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Awais_Belal@mentor.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=martin.jansa@gmail.com \
/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