From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Recent xserver-kdrive failure and util-macros update
Date: Wed, 4 Jan 2012 16:24:39 +0800 [thread overview]
Message-ID: <4F040CC7.7070500@windriver.com> (raw)
In-Reply-To: <4F03FFB2.8040606@linux.intel.com>
On 2012年01月04日 15:28, Saul Wold wrote:
>
> We seem to have a relatively new failure in xserver-kdrive, which
> appeared in the last set of change. I tried to run though a bisect but
> was not able to find the problem.
>
> The problem seems to be related to configure.ac setting of
> XSERVER_CFLAGS='$(CWARNFLAGS)' and then using -Werror=address, which
> is what causes the failure.
>
> This seems to be related to the util-macros update to 1.16, which adds
> more warnings to errors. Since we are still using the older
> xserver-kdrive, there are warnings that are now errors with the update.
>
> We could patch the current xserver-kdrive, revert the 1.16 update to
> util-macros or update xserver-kdrive (which is in the works, but I
> think had some issues). This also seems to affect the libxp package on
> x86-64.
>
> Thoughts, I know we don't like to revert, but we may have to in this
> case as we don't have the kdrive update yet and would need to further
> investigate the libxp failure.
>
Hi Saul,
Do you have any suggestion my previous patches to update xserver-kdrive ?
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/update
next prev parent reply other threads:[~2012-01-04 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 7:28 Recent xserver-kdrive failure and util-macros update Saul Wold
2012-01-04 8:24 ` Xiaofeng Yan [this message]
2012-01-04 10:18 ` Cui, Dexuan
2012-01-04 17:39 ` Khem Raj
2012-01-04 19:45 ` Gary Thomas
2012-01-04 20:08 ` Saul Wold
2012-01-04 20:36 ` Gary Thomas
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=4F040CC7.7070500@windriver.com \
--to=xiaofeng.yan@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox