All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<Openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] mtools, syslinux: add ability to compile with nativesdk
Date: Wed, 30 Oct 2013 21:31:29 -0500	[thread overview]
Message-ID: <5271C101.2050802@windriver.com> (raw)
In-Reply-To: <CAMKF1srsz3njDJpvm4sr865VDkWtemeZzDshT2gY05noNqZZLA@mail.gmail.com>

On 10/30/2013 06:47 PM, Khem Raj wrote:
> On Wed, Oct 30, 2013 at 3:48 PM, Jason Wessel
> <jason.wessel@windriver.com> wrote:
>> For regenerating and ISO or EFI boot image the nativesdk needs mtools
>> and syslinux.
>>
>> Both recipes are patched in one patch since syslinux requires
>> mtools.
>>
> as they depend on eglibc/glibc only. Can you also make sure that they
> get flagged when building
> systems with non-eglibc C libraries.


Is there an example in a recipe of what you are talking about?

I saw in another recipe:
python __anonymous() {
    if d.getVar("TARGET_OS", True) != "linux":
        return
    if d.getVar("TCLIBC", True) == "eglibc":
        raise bb.parse.SkipPackage("libiconv is provided for use with uClibc only - eglibc already provides iconv")
}

Or is there a build test I should be using to test with uClibc for when things like this change in general?

Thanks,
Jason.


  reply	other threads:[~2013-10-31  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 22:48 [PATCH] mtools, syslinux: add ability to compile with nativesdk Jason Wessel
2013-10-30 23:47 ` Khem Raj
2013-10-31  2:31   ` Jason Wessel [this message]
2013-10-31  2:36     ` Khem Raj

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=5271C101.2050802@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 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.