From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Jens Rehsack <rehsack@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Jens Rehsack <sno@netbsd.org>
Subject: Re: [OE-core][PATCH] toolchain-scripts.bbclass: also recognize ${SDK_SYS} env setups
Date: Wed, 8 Jul 2020 18:20:46 -0300 [thread overview]
Message-ID: <CAP9ODKosgPup-Y3Ee-of+N9d9t+3GPHfZ4ZkfpE8PhJoxAkjTg@mail.gmail.com> (raw)
In-Reply-To: <20200708195756.760-1-sno@netbsd.org>
Em qua., 8 de jul. de 2020 às 16:58, Jens Rehsack <rehsack@gmail.com> escreveu:
>
> Instead of recognizing only environment-setup scripts in
> ${STAGING_DIR_TARGET} or ${STAGING_DIR_NATIVE}, respectively - lurk also into
> ${SDKPATH}/buildtools/sysroots/${SDK_SYS} where nativesdk-openssl installs
> setup files.
>
> Remove overwriting of OPENSSL_CONF from buildtools-tarball.bb to clarify
> whether nativesdk-openssl installs wrong content or buildtools-tarball:
> (nativesdk-openssl) tmp/sysroots/x86_64/usr/lib/ssl-1.1/openssl.cnf
> (buildtools-tarball) buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/openssl.cnf
>
> Signed-off-by: Jens Rehsack <sno@netbsd.org>
I did not understand the openssl related change. Is it possible to
rework the commit log so it is more detailed?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2020-07-08 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:57 [OE-core][PATCH] toolchain-scripts.bbclass: also recognize ${SDK_SYS} env setups Jens Rehsack
2020-07-08 21:20 ` Otavio Salvador [this message]
2020-07-09 4:13 ` Jens Rehsack
2020-07-09 11:52 ` Otavio Salvador
2020-07-09 13:16 ` Jens Rehsack
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=CAP9ODKosgPup-Y3Ee-of+N9d9t+3GPHfZ4ZkfpE8PhJoxAkjTg@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=openembedded-core@lists.openembedded.org \
--cc=rehsack@gmail.com \
--cc=sno@netbsd.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.