Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] selftest/pkgdata: support musl on unit tests
Date: Thu, 30 Mar 2017 08:38:21 -0600	[thread overview]
Message-ID: <1490884701.17259.52.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0Lbb-TZYaZs+aKMSZEKUAhcN=8n6+bDrq5GjaTxo-Ws-cw@mail.gmail.com>

On Thu, 2017-03-30 at 12:45 +0100, Burton, Ross wrote:
> 
> On 30 March 2017 at 07:39,
> <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
>         +        # recipe-runtime-package relation for virtual/libc
>         provider
>         +        Libc = collections.namedtuple('Libc', ['recipe',
>         'runtime_pkg', 'libpath', 'staticdev', 'utils', 'rutils'])
>         +        cls.libc = Libc('glibc', 'libc6', '/lib/libc.so.6',
>         'libc6-staticdev', 'glibc-utils', 'lib6-utils')
>         +        if get_bb_var('TCLIBC') == 'musl':
>         +            cls.libc = Libc('musl', 'musl',
>         '/usr/lib/libc.so', 'musl-staticdev', None, None)
>         
> 
> Instead of all of this, why not just change the tests to use a
> different package?  The bulk of them were just using glibc as it's
> going to be built, but we've built zlib too so the tests could use
> that instead.

If you consider that replacing the libc for another recipe/package is
fine, I go that way.

Leo
> 
> 
> Ross




      reply	other threads:[~2017-03-30 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  6:39 [PATCH] selftest/pkgdata: support musl on unit tests leonardo.sandoval.gonzalez
2017-03-30 11:45 ` Burton, Ross
2017-03-30 14:38   ` Leonardo Sandoval [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=1490884701.17259.52.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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