Well, if I may say (I'm probably more of a bother than helping here...),

Mesa doesn't compile correctly on my alpha. I think the problem is that
the alpha kernel tree (asm dir) doesn't have mtrr.h

This is what it looks like:

gcc -mieee -Wall -Wno-uninitialized -O3 -fexpensive-optimizations
-fomit-frame-pointer -finline-functions -funroll-loops -DNDEBUG
-DMGA_LOG_ENABLED -DGLX_LOG -DHW_ACCEL -DDYNAMIC_MODULE -DXFreeXDGA  
-DMESA_PATCH  -DGLXEXT -DXDEBUG -DMESA31 -DBUILD_COLOR_TABLE_EXT=1
-DGLX_MODULE -I../.. -I../../serverglx -I../../../include
-I/usr/src/RPM/BUILD/Mesa-3.2dev/include
-I../../../xc-headers/programs/Xserver/hw/xfree86/vga256/drivers/mga
-I../../../xc-headers/programs/Xserver/hw/xfree86/common_hw
-I../../../xc-headers/programs/Xserver/hw/xfree86/common
-I../../../xc-headers/programs/Xserver/hw/xfree86/vga256/vga
-I../../../xc-headers/programs/Xserver/hw/xfree86/os-support
-I../../../xc-headers/programs/Xserver/hw/xfree86
-I../../../xc-headers/programs/Xserver/include
-I../../../xc-headers/include/fonts -I../../../xc-headers/include
-I/usr/src/RPM/BUILD/Mesa-3.2dev/src -I/usr/X11R6/include -D_XSERVER64
-fPIC -c mgadirect.c
mgadirect.c:47: asm/mtrr.h: No such file or directory
make[3]: *** [mgadirect.o] Error 1
make[3]: Leaving directory
`/usr/src/RPM/BUILD/Mesa-3.2dev/glx-19991126/servGL/hwglx/mga'
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory
`/usr/src/RPM/BUILD/Mesa-3.2dev/glx-19991126/servGL/hwglx'
make[1]: *** [glx-mga.so] Error 1
make[1]: Leaving directory
`/usr/src/RPM/BUILD/Mesa-3.2dev/glx-19991126/servGL'
make: *** [all] Error 1
Bad exit status from /var/tmp/rpm-tmp.18609 (%build)

OK. If we could have an arechitecture selection in the .spec file for
compiling the
glx stuff, then I think it would work. On the alpha (and other weird
platforms) we
don't compile the non-supported stuff...

Could this be a start: ??

cd glx-%{glx_ver}
if arch alpha alphaev56
./autogen.sh --with-chipset=both --with-mesa=../ --enable-extra
--enable-agp --prefix=/usr/X11R6 --sysconfdir=/etc
--target=%{_target_cpu}-mandrake-linux-gnu
endif
 
if arch i386 i486 i568 i686
./autogen.sh --with-chipset=both --with-mesa=../ --enable-extra
--enable-mtrr --enable-agp --prefix=/usr/X11R6 --sysconfdir=/etc
--target=%{_target_cpu}-mandrake-linux-gnu
endif

Greetings,

Stefan

> > Right,

> > I had the same problems (added to the new Mesa compatibility...)
> 
> now is a really really good time for mesa complaints, below is a list of
> all i know that need relinked (at the very least)
> --
> 
> --
> I also need feedback on software, glx-tnt, and glide functionality.
> The glx-mga module cranks 450-500fps out of gears with the "agpgart"
> module.
> 
> > At the end of the install, you have to go to the F2 console and create a
> > symbolic link to vmlinuz.
> 
> Don't forget todo this, I did it sucked big time (make sure initscripts
> is installed while your there, mine weren't)
> 
> > It should then finish the install (with an error message for an unavailable
> > X font). BUT... it won't boot because it doesn't find the inittab and there
> > is no prompt and no delay.
> 
> Pixel, the X test trys to use the font server..
> 
> > At boot time, press the right shift key, which gives you the login prompt.
> > Then type 'linux init=/etc/inittab', and it should boot.
> 
> shift-tab halts the timer.
> 
> > run lilo correctly and it should go.
> >
> > ---
> > kk1
> >
> > >From: Sergio Korlowsky <[EMAIL PROTECTED]>
> > >Reply-To: [EMAIL PROTECTED]
> > >To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> > >Subject: [Cooker] (cooker) Still a few errors
> > >Date: Sat, 04 Dec 1999 18:51:56 -0600
> > >
> > >There is no question about getting bettter and better everyday,
> > >
> > >but I still having a few problems at installation.
> > >
> > >in the last few days I have been experiencing a new error, while
> > >installing and after selecting packages for installation,
> > >I got this error message:
> > >
> > >There was an error ordering packages.
> > >loop in prerequisite chain:basesystem setup tcsh fileutils info bash
> > >glibc
> > >ldconfig basesystem go on anyway
> > >
> > >       yes       no
> 
> This an old problem i introduced in the installer while makeing the
> install.log look pretty (not all the info pages got installed in %post's)
> Apparently pixel was sick of the hack-around he did for it originaly and
> he's tackleing the real problem :)
> 
> > >I choose yes, and at the end it reads it can't find kernel package
> 
> no initscripts, and /boot/vmlinuz symlink, answers above :)
> 
> > >then it fails to install the boot loader...
> > >
> > >Sergio Korlowsky
> > >
> > >OTH... I tried an 'upgrade from Helios (6.1)
> > >
> > >and it went thru without a problem  (?)

Reply via email to