Re: [Mesa3d-users] [Fwd: r600_cmdbuf.c:323: error: storage size of ‘cs_cmd’ isn’t known]

[Chris J. <cjn...@gm...>]

On Sun, Aug 02, 2009 at 01:12:54AM EDT, Arthur Marsh wrote:
> Hi, I'm trying to build mesa using the instructions at:
> 
> http://www.x.org/wiki/radeonhd%3Aexperimental_3D
> 
> and get the error:
> 
> make[5]: Entering directory `/usr/src/sound/mesa/src/mesa/drivers/dri/r600'
> gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> -I../../../../../include -I../../../../../src/mesa
> -I../../../../../src/egl/main -I../../../../../src/egl/drivers/dri
> -I/usr/include/drm    -g -O2 -Wall -Wmissing-prototypes -std=c99
> -ffast-math -fno-strict-aliasing -g  -fPIC  -DUSE_X86_64_ASM
> -D_GNU_SOURCE -DPTHREADS -DDEBUG -DHAVE_POSIX_MEMALIGN
> -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING
> -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS  -DCOMPILE_R600 -DR200_MERGED=0
> -DRADEON_COMMON=1 -DRADEON_COMMON_FOR_R600  r600_cmdbuf.c -o r600_cmdbuf.o
> r600_cmdbuf.c: In function ‘r600_cs_emit’:
> r600_cmdbuf.c:323: error: storage size of ‘cs_cmd’ isn’t known
> r600_cmdbuf.c:324: error: array type has incomplete element type
> r600_cmdbuf.c:342: error: ‘RADEON_CHUNK_ID_IB’ undeclared (first use in
> this function)
> r600_cmdbuf.c:342: error: (Each undeclared identifier is reported only once
> r600_cmdbuf.c:342: error: for each function it appears in.)
> r600_cmdbuf.c:347: error: ‘RADEON_CHUNK_ID_RELOCS’ undeclared (first use
> in this function)
> r600_cmdbuf.c:362: error: ‘DRM_RADEON_CS’ undeclared (first use in this
> function)
> r600_cmdbuf.c:324: warning: unused variable ‘cs_chunk’
> r600_cmdbuf.c:323: warning: unused variable ‘cs_cmd’
> make[5]: *** [r600_cmdbuf.o] Error 1
> 
> Any suggestions?
> 
> Arthur.
> 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-users
From: Chris Jones <cjn...@gm...>
To: Andrei Popescu <and...@gm...>
Cc: 
Bcc: 
Subject: Re: vim linebreaks in Mutt
Reply-To: 
In-Reply-To: <20090802073214.GC4006@think.homelan>

On Sun, Aug 02, 2009 at 03:32:14AM EDT, Andrei Popescu wrote:
> On Sat,01.Aug.09, 21:56:46, Rob Owens wrote:
> > What's the proper setting to get good line breaks in Mutt (using vim),
> > without manually hitting the enter key?  (So that this paragraph, for
> > instance, is not one long line of text, but rather several shorter lines of
> > text).
> > 
> > I currently have this in .muttrc:
> > 
> > set editor="vim -c 'set wrapmargin=5'"
> 
> If filetype plugins are active[1] vim should "know" you are editing a 
> mail and will already set textwidth=72 and use also some syntax coloring 
> (ex. quotes and your .sig will show in a different color). 
> 
> Additionally I have this in my .vimrc
> 
> autocmd FileType mail set spell spelllang=ro,de,en fo+=aw       " spell and autowrap text in emails
> 
> [1] they have been disabled by default in Debian, but my .vimrc is based 
> on the example in /usr/share/vim/vimcurrent/vimrc_example.vim which 
> enables them
> 
> Regards,
> Andrei
> -- 
> If you can't explain it simply, you don't understand it well enough.
> (Albert Einstein)