Actually I did have libexpat statically linked, but as you can see... test "$BRANCH" == config-0-0-1-branch && sed -i -e 's/-lexpat/-Wl,-Bstatic -lexpat -Wl,-Bdynamic/' build/$BRANCH/xc/config/cf/X11.tmpl
... just on config-0-0-1-branch, because the config-0-0-1-branch hadn't been merged into the trunk at that time yet. I've fixed this now and I'll fire a snapshot build to verify it. Still, sorry for not noticing this earlier... Jose Fonseca On Tue, Nov 25, 2003 at 02:48:48PM +0000, José Fonseca wrote: > On Tue, Nov 25, 2003 at 01:27:32PM +0100, Felix Kühling wrote: > > > Ian Romanick wrote: > > > > This is getting old. This makes at least 10 reports of "direct > > > > rendering not working" that turned out to be libexpat.so > > > > problems. Are we or are we not staticly linking with libexpat > > > > for the nightly builds? I seriously thought that this was > > > > resolved weeks ago. > > No we aren't... > > > Apperently we're not linking statically with libexpat. This is > > really only a snapshot problem, so doing this dlopen thing would be > > overkill. As jfonseca doesn't seem to have much time to maintain > > the snapshots I'd volunteer to setup a snapshot build on > > freedesktop.org that would link statically with libexpat. I believe > > I could start building snapshots by the end of this week. If > > someone's quicker than tat, go ahead ;-) > > Sorry. I forgot to flag your reply describing how to link statically > and never remembered the subject again (at that time I was more > concerned with the build failure...) I'm taking care of it now. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
