Menu
▾
▴
mesa3d-dev
|
From: STEVE555 <ste...@ho...> - 2010-03-24 12:43:21
|
Hi everyone,
I pulled the latest commits from the git repository last
night and did a gmake -B realclean,and did ./configure with these options:
./configure --prefix=/usr --enable-32-bit --enable-xcb
--enable-gallium-nouveau --with-state-trackers=dri,egl,xorg,glx,vega,es
--enable-motif --enable-gl-osmesa --disable-gallium-intel
--disable-gallium-radeon --with-expat=/usr/lib
--with-demos=xdemos,demos,trivial,tests --with-dri-drivers=swrast
--enable-gallium-swrast --enable-gallium-svga --with-max-width=4096
--with-max-height=4096 --enable-debug
I then ran gmake,but when the build gets to the xorg state-tracker,I keep
hitting this error:
gmake[4]: Leaving directory `/opt/mesa/src/gallium/state_trackers/xorg'
gmake[4]: Entering directory `/opt/mesa/src/gallium/state_trackers/glx'
gmake[5]: Entering directory `/opt/mesa/src/gallium/state_trackers/glx/xlib'
rm -f depend
touch depend
/usr/bin/makedepend -fdepend -I/usr/lib/gcc/i686-redhat-linux/4.4.3/include
-I. -I../../../../../src/gallium/include
-I../../../../../src/gallium/auxiliary -I../../../../../src/gallium/drivers
-I../../../../../include -I../../../../../src/mesa @X11_CFLAGS@ glx_api.c
glx_getproc.c glx_usefont.c xm_api.c xm_st.c 2> /dev/null
gmake[5]: Leaving directory `/opt/mesa/src/gallium/state_trackers/glx/xlib'
gmake[5]: Entering directory `/opt/mesa/src/gallium/state_trackers/glx/xlib'
gcc -c -I. -I../../../../../src/gallium/include
-I../../../../../src/gallium/auxiliary -I../../../../../src/gallium/drivers
-I../../../../../include -I../../../../../src/mesa @X11_CFLAGS@ -g -O2 -Wall
-Wmissing-prototypes -std=c99 -ffast-math -fvisibility=hidden
-fno-strict-aliasing -m32 -g -fPIC -m32 -DUSE_X86_ASM -DUSE_MMX_ASM
-DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_GNU_SOURCE -DPTHREADS -DDEBUG
-DHAVE_POSIX_MEMALIGN -DUSE_XCB -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER
-DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS
-DHAVE_XEXTPROTO_71 -DMAX_WIDTH=4096 -DMAX_HEIGHT=4096 glx_api.c -o
glx_api.o
gcc: @X11_CFLAGS@: No such file or directory
gmake[5]: *** [glx_api.o] Error 1
gmake[5]: Leaving directory `/opt/mesa/src/gallium/state_trackers/glx/xlib'
gmake[4]: *** [subdirs] Error 1
gmake[4]: Leaving directory `/opt/mesa/src/gallium/state_trackers/glx'
gmake[3]: *** [subdirs] Error 1
gmake[3]: Leaving directory `/opt/mesa/src/gallium/state_trackers'
gmake[2]: *** [default] Error 1
gmake[2]: Leaving directory `/opt/mesa/src/gallium'
gmake[1]: *** [subdirs] Error 1
gmake[1]: Leaving directory `/opt/mesa/src'
gmake: *** [default] Error 1
Regards,
STEVE555
--
View this message in context: http://old.nabble.com/Build-Error-with-Xorg-State-Tracker-tp28014534p28014534.html
Sent from the mesa3d-dev mailing list archive at Nabble.com.
|
|
From: Jakob B. <wal...@gm...> - 2010-03-24 13:14:13
|
On Wed, Mar 24, 2010 at 1:43 PM, STEVE555 <ste...@ho...> wrote: > > Hi everyone, > I pulled the latest commits from the git repository last > night and did a gmake -B realclean,and did ./configure with these options: Re-run autogen.sh Cheers Jakob. |
|
From: STEVE555 <ste...@ho...> - 2010-03-24 14:15:41
|
Dear Jakob,
I did a ./autogen.sh and Mesa builds fine now,sorry about
that.I do run ./autogen.sh from time to time,I just thought ./configure
would be enough,oh well,I like to thank you for your help.
Regards,
STEVE555
STEVE555 wrote:
>
> Hi everyone,
> I pulled the latest commits from the git repository last
> night and did a gmake -B realclean,and did ./configure with these options:
>
> ./configure --prefix=/usr --enable-32-bit --enable-xcb
> --enable-gallium-nouveau --with-state-trackers=dri,egl,xorg,glx,vega,es
> --enable-motif --enable-gl-osmesa --disable-gallium-intel
> --disable-gallium-radeon --with-expat=/usr/lib
> --with-demos=xdemos,demos,trivial,tests --with-dri-drivers=swrast
> --enable-gallium-swrast --enable-gallium-svga --with-max-width=4096
> --with-max-height=4096 --enable-debug
>
> I then ran gmake,but when the build gets to the xorg state-tracker,I keep
> hitting this error:
>
> gmake[4]: Leaving directory `/opt/mesa/src/gallium/state_trackers/xorg'
> gmake[4]: Entering directory `/opt/mesa/src/gallium/state_trackers/glx'
> gmake[5]: Entering directory
> `/opt/mesa/src/gallium/state_trackers/glx/xlib'
> rm -f depend
> touch depend
> /usr/bin/makedepend -fdepend
> -I/usr/lib/gcc/i686-redhat-linux/4.4.3/include -I.
> -I../../../../../src/gallium/include
> -I../../../../../src/gallium/auxiliary
> -I../../../../../src/gallium/drivers -I../../../../../include
> -I../../../../../src/mesa @X11_CFLAGS@ glx_api.c glx_getproc.c
> glx_usefont.c xm_api.c xm_st.c 2> /dev/null
> gmake[5]: Leaving directory
> `/opt/mesa/src/gallium/state_trackers/glx/xlib'
> gmake[5]: Entering directory
> `/opt/mesa/src/gallium/state_trackers/glx/xlib'
> gcc -c -I. -I../../../../../src/gallium/include
> -I../../../../../src/gallium/auxiliary
> -I../../../../../src/gallium/drivers -I../../../../../include
> -I../../../../../src/mesa @X11_CFLAGS@ -g -O2 -Wall -Wmissing-prototypes
> -std=c99 -ffast-math -fvisibility=hidden -fno-strict-aliasing -m32 -g
> -fPIC -m32 -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM
> -D_GNU_SOURCE -DPTHREADS -DDEBUG -DHAVE_POSIX_MEMALIGN -DUSE_XCB
> -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING
> -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -DHAVE_XEXTPROTO_71 -DMAX_WIDTH=4096
> -DMAX_HEIGHT=4096 glx_api.c -o glx_api.o
> gcc: @X11_CFLAGS@: No such file or directory
> gmake[5]: *** [glx_api.o] Error 1
> gmake[5]: Leaving directory
> `/opt/mesa/src/gallium/state_trackers/glx/xlib'
> gmake[4]: *** [subdirs] Error 1
> gmake[4]: Leaving directory `/opt/mesa/src/gallium/state_trackers/glx'
> gmake[3]: *** [subdirs] Error 1
> gmake[3]: Leaving directory `/opt/mesa/src/gallium/state_trackers'
> gmake[2]: *** [default] Error 1
> gmake[2]: Leaving directory `/opt/mesa/src/gallium'
> gmake[1]: *** [subdirs] Error 1
> gmake[1]: Leaving directory `/opt/mesa/src'
> gmake: *** [default] Error 1
>
> Regards,
> STEVE555
>
--
View this message in context: http://old.nabble.com/Build-Error-with-Xorg-State-Tracker-tp28014534p28015450.html
Sent from the mesa3d-dev mailing list archive at Nabble.com.
|
|
From: Dan N. <dbn...@gm...> - 2010-03-26 13:49:10
|
On Wed, Mar 24, 2010 at 07:00:06AM -0700, STEVE555 wrote: > > Dear Jakob, > I did a ./autogen.sh and Mesa builds fine now,sorry about > that.I do run ./autogen.sh from time to time,I just thought ./configure > would be enough,oh well,I like to thank you for your help. When someone makes a commit to configure.ac, the configure file has to be regenerated. Usually automake adds rules so that if configure.ac is newer than configure, it runs autoconf again. We can try to add some rules like that to the toplevel Makefile, but I'd like to take a look at the way automake does it before adding some half baked hack. However, the takeaway is that if you're seeing build errors, you'll want to check that configure is up to date and that it's been run again. Here's a handy trick for regenerating the autotools and keeping your configure arguments: $ autoreconf -iv && ./config.status --recheck && ./config.status That's pretty much a surefire way to ensure the autotools (whichever ones) are refreshed, and the second part runs configure again with your arguments you used before. -- Dan |
|
From: STEVE555 <ste...@ho...> - 2010-03-26 23:53:07
|
Hi all,
Sorry for the late reply.I've just tried Dan's trick and it works
very well,thank you very much for the tip.
Regards,
STEVE555
Dan Nicholson-2 wrote:
>
> On Wed, Mar 24, 2010 at 07:00:06AM -0700, STEVE555 wrote:
>>
>> Dear Jakob,
>> I did a ./autogen.sh and Mesa builds fine now,sorry
>> about
>> that.I do run ./autogen.sh from time to time,I just thought ./configure
>> would be enough,oh well,I like to thank you for your help.
>
> When someone makes a commit to configure.ac, the configure file has to
> be regenerated. Usually automake adds rules so that if configure.ac is
> newer than configure, it runs autoconf again. We can try to add some
> rules like that to the toplevel Makefile, but I'd like to take a look at
> the way automake does it before adding some half baked hack.
>
> However, the takeaway is that if you're seeing build errors, you'll want
> to check that configure is up to date and that it's been run again.
>
> Here's a handy trick for regenerating the autotools and keeping your
> configure arguments:
>
> $ autoreconf -iv && ./config.status --recheck && ./config.status
>
> That's pretty much a surefire way to ensure the autotools (whichever
> ones) are refreshed, and the second part runs configure again with your
> arguments you used before.
>
> --
> Dan
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Mesa3d-dev mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
>
>
--
View this message in context: http://old.nabble.com/Build-Error-with-Xorg-State-Tracker-tp28014534p28049154.html
Sent from the mesa3d-dev mailing list archive at Nabble.com.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X