All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Ferland <ferlandm@sonatest.com>
To: yocto@yoctoproject.org
Subject: xserver-xorg
Date: Mon, 16 Jul 2012 13:56:20 -0400	[thread overview]
Message-ID: <87sjcrio8r.fsf@sonatest.com> (raw)

Hi all,

I'm having trouble building the xserver-xorg package. The build fails
with:

| render2.c: In function '__glXDisp_Map1d':
| render2.c:104:5: error: the comparison will always evaluate as 'true' for the address of 'u1' will never be NULL [-Werror=address]
| render2.c:105:5: error: the comparison will always evaluate as 'true' for the address of 'u2' will never be NULL [-Werror=address]
| render2.c: In function '__glXDisp_Map2d':
| render2.c:147:5: error: the comparison will always evaluate as 'true' for the address of 'u1' will never be NULL [-Werror=address]
| render2.c:148:5: error: the comparison will always evaluate as 'true' for the address of 'u2' will never be NULL [-Werror=address]
| render2.c:149:5: error: the comparison will always evaluate as 'true' for the address of 'v1' will never be NULL [-Werror=address]
| render2.c:150:5: error: the comparison will always evaluate as 'true' for the address of 'v2' will never be NULL [-Werror=address]
| cc1: some warnings being treated as errors

The target machine is a x86_64. Looks like the compiler doesn't like how
the __GLX_GET_DOUBLE macro tests the address of stack variables against
NULL.

I would like to know if there is a patch upstream or if this is a known
issue? What surprises me the most is that this machine looks a lot like
the meta-sugarbay which builds correctly.

Regards,

Marc


             reply	other threads:[~2012-07-16 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 17:56 Marc Ferland [this message]
2012-07-17  7:01 ` xserver-xorg Laurentiu Palcu
2012-07-17 13:22   ` xserver-xorg Marc Ferland
2012-07-17 13:46     ` xserver-xorg Paul Eggleton

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=87sjcrio8r.fsf@sonatest.com \
    --to=ferlandm@sonatest.com \
    --cc=yocto@yoctoproject.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.