Re: [Dri-devel] Re: Build strangeness

[Nathaniel G. <n8...@ca...>]

On Wednesday 06 August 2003 02:16 pm, Michel D=C3=A4nzer wrote:
> On Wed, 2003-08-06 at 23:09, Nathan Gray wrote:
> > Felix K=C3=BChling wrote:
> > > On Tue, 05 Aug 2003 20:59:32 -0700
> > >
> > > Nathan Gray <n8...@ca...> wrote:
> > >> Hello,
> > >>
> > >> I'm trying to build from CVS but I'm seeing something
> > >> unexpected.  The build
> > >> is trying to link to X libraries outside of the DRI tree itself.
> > >>  In host.def I altered the ProjectRoot variable as so:
> > >
> > > Leif Delgass describes a procedure to build DRI in a new
> > > ProjectRoot directory on his mach64 pages:
> > > http://www.retinalburn.net/linux/dri_HOWTO.html. It's similar to
> > > what Ian described, except that you make symbolic links instead
> > > of copying all the libs and headers. make install will overwrite
> > > everything that is rebuilt from DRI sources.
> > >
> > > Not that Leif uses the -ignorelinks option to lndir. I believe
> > > it's better to go without -ignorelinks. Works for me for ages.
> >
> > This is a good idea.  I thought of trying this but it's good to
> > know that it works.  I've also added this info to the FAQ.
>
> This shouldn't be necessary at all though - have you tried the patch
> I posted?

I haven't tried it yet.  In the end I decided to use the dripkg.sh=20
script to wrap things up into a form I'm more familiar with.  I'll=20
explore other options later.

> > I have one last question.  Is it safe to have mismatched foo_dri.so
> > and foo_drv.o?  I'm using a CVS version of radeon_drv.o that has
> > several fixes that I can't do without, but I'd also like to get
> > some of the recent fixes to the radeon DRI driver.  So can I just
> > upgrade radeon_dri.so and the radeon.o kernel modules?
>
> Sure.

Good to be sure.  Thanks,
-n8

--=20
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->