linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Gareth Hughes <gareth@valinux.com>
Cc: "Timothy A. Seufert" <tas@mindspring.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: r128 DRI driver now fully functional on PPC
Date: Mon, 26 Feb 2001 11:21:10 +0100	[thread overview]
Message-ID: <3A9A2E16.6F679EF3@iiic.ethz.ch> (raw)
In-Reply-To: 3A9A2A9D.8A779B@valinux.com


Gareth Hughes wrote:
>
> Michel Dänzer wrote:
> >
> > "Timothy A. Seufert" wrote:
> > >
> > > At 9:02 PM +1100 2/23/01, Gareth Hughes wrote:
> > >
> > > >Run with LIBGL_DEBUG=1 and see what it says.
> > >
> > > This revealed what was happening.
> > >
> > > I set the project root to /usr/Xgart to avoid having to overwrite my
> > > existing X11 installation.  libGL was trying to load r128_dri.so, but
> > > it was looking under /usr/X11R6/lib/modules/dri, which doesn't even
> > > exist.
> >
> > Strange, it should look in <ProjectRoot>/lib/modules/dri/ . Seems it
> > didn't pick up the right libGL.
>
> I'd say libGL.so is doing dlopen( "modules/dri/r128_dri.so", ... ) and
> thus picking up the first instance of that in the dynamic loader's
> path.  Similarly, applications linked with -lGL will pick up the first
> instance of libGL.so, not necessarily the one residing under the current
> X server's ProjectRoot directory.

First I thought I'd stand corrected, but on second thought - it looks for
/usr/X11R6-DRI/lib/modules/dri/r128_dri.so on my machine (if ProjectRoot is
/usr/X11R6-DRI), but /usr/X11R6-DRI/lib isn't in ld.so.conf . It even looks
there if I set LD_LIBRARY_PATH to the exports/lib directory in the build tree.


Am I still not getting it? :)


--
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-02-26 10:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  8:08 r128 DRI driver now fully functional on PPC Gareth Hughes
2001-01-31 11:49 ` Benjamin Herrenschmidt
2001-01-31 14:54   ` [linux-fbdev] " Andreas Hundt
2001-01-31 18:32     ` Michel Dänzer
2001-01-31 18:43       ` Geert Uytterhoeven
2001-01-31 18:53         ` Michel Dänzer
2001-01-31 19:14         ` Andreas Hundt
2001-01-31 16:49   ` Kostas Gewrgiou
2001-01-31 18:26   ` Michel Dänzer
2001-02-23  7:07 ` Timothy A. Seufert
2001-02-23 10:02   ` Gareth Hughes
2001-02-25  8:32     ` Timothy A. Seufert
2001-02-26  9:39       ` Michel Dänzer
2001-02-26 10:06         ` Gareth Hughes
2001-02-26 10:21           ` Michel Dänzer [this message]
2001-02-26 10:28             ` Gareth Hughes
2001-02-27 10:03               ` Timothy A. Seufert
2001-02-27 11:39                 ` Gareth Hughes
2001-02-27 21:43                   ` Michel Dänzer
2001-02-23 12:19   ` Michel Dänzer
2001-02-23 12:23     ` Gareth Hughes
2001-02-23 12:33       ` Michel Dänzer

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=3A9A2E16.6F679EF3@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=gareth@valinux.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tas@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).