From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Seebach <peter.seebach@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] eglibc-use-option-groups.patch: Several fixups
Date: Sat, 08 Nov 2014 14:42:45 +0000 [thread overview]
Message-ID: <1415457765.2820.21.camel@linuxfoundation.org> (raw)
In-Reply-To: <d2ce73488a8afb7a8d10286da138810d30b4a4be.1415390286.git.peter.seebach@windriver.com>
On Fri, 2014-11-07 at 13:59 -0600, Peter Seebach wrote:
> This incorporates suggested changes for issues 6797 and 6809 from
> bugzilla, and a proposed change for 6796. For 6796, the issue is
> that you can't just include <gnu/option-groups.h> in libc-symbols,
> so we may not always have the option group defines available. The
> workaround is to just leave the HAVE_MBSTATE_T definition visible;
> the obvious relevant usage is already also conditionalized on
> the option group locale define by this patch. This might not fix
> all the cases if the locale group isn't enabled, but it eliminates a
> pretty large raft of -Wundef warnings.
>
> The reason HAVE_MBSTATE_T wasn't conditionalized in 2.19 is that
> it didn't exist in 2.19.
>
> Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Whilst I haven't 100% confirmed it,
https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/102/steps/BuildImages/logs/stdio
looks like it may well be as a result of this change (which was included
in the master-next build in question)...
Cheers,
Richard
next prev parent reply other threads:[~2014-11-08 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:59 [PATCH 0/1] eglibc option groups fixup Peter Seebach
2014-11-07 19:59 ` [PATCH 1/1] eglibc-use-option-groups.patch: Several fixups Peter Seebach
2014-11-08 14:42 ` Richard Purdie [this message]
2014-11-10 19:00 ` Peter Seebach
2014-11-11 10:55 ` Richard Purdie
2014-11-11 18:29 ` Peter Seebach
2014-11-18 18:46 ` Juro Bystricky
2014-11-19 17:59 ` Juro Bystricky
2014-11-19 20:09 ` Peter Seebach
2014-11-20 18:59 ` Juro Bystricky
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=1415457765.2820.21.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.seebach@windriver.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.