From: Brian Paul <brianp@vmware.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>
Cc: DRI <dri-devel@lists.sourceforge.net>,
"mesa3d-dev@lists.sourceforge.net"
<mesa3d-dev@lists.sourceforge.net>
Subject: Re: [Mesa3d-dev] [mesa] svga: Fix error: cannot take address of bit-field 'texture_target' in svga_tgsi.h
Date: Wed, 06 Jan 2010 10:07:36 -0700 [thread overview]
Message-ID: <4B44C358.2020005@vmware.com> (raw)
In-Reply-To: <2d0a357f1001060834k23c2ad38pa2111565f6defa42@mail.gmail.com>
Sedat Dilek wrote:
> Hi,
>
> this patch fixes a build-error in mesa GIT master after...
>
> commit 251363e8f1287b54dc7734e690daf2ae96728faf (patch)
> "configs: set INTEL_LIBS, INTEL_CFLAGS, etcmaster"
>
>>From my build-log:
> ...
> In file included from svga_pipe_fs.c:37:
> svga_tgsi.h: In function 'svga_fs_key_size':
> svga_tgsi.h:122: error: cannot take address of bit-field 'texture_target'
> make[4]: *** [svga_pipe_fs.o] Error 1
>
> Might be introduced in...
>
> commit 955f51270bb60ad77dba049799587dc7c0fb4dda
> "Make sure we use only signed/unsigned ints with bitfields."
>
> Kind Regars,
> - Sedat -
>
I just fixed that.
-Brian
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
next prev parent reply other threads:[~2010-01-06 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 16:34 [mesa] svga: Fix error: cannot take address of bit-field 'texture_target' in svga_tgsi.h Sedat Dilek
2010-01-06 17:07 ` Brian Paul [this message]
2010-01-06 17:09 ` Sedat Dilek
2010-01-06 17:38 ` Keith Whitwell
2010-01-06 17:38 ` Brian Paul
2010-01-06 17:55 ` [Mesa3d-dev] " Sedat Dilek
2010-01-06 17:39 ` michal
2010-01-06 17:54 ` Sedat Dilek
2010-01-08 14:34 ` michal
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=4B44C358.2020005@vmware.com \
--to=brianp@vmware.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=mesa3d-dev@lists.sourceforge.net \
--cc=sedat.dilek@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.