John Martin wrote:
> Alan Coopersmith wrote:
>>
>> *sigh*   MakeAtom is one of a bunch of symbols in libXfont that are 
>> supposed to be weak symbols so that they aren't used if a real 
>> definition is in place, but
>> they're only marked weak with gcc attributes, not Sun cc pragmas.
>>
> FWIW, the StudioExpress February early access release does support
> the gcc attribute syntax:

Cool.    Unfortunately, we're stuck building with older versions of
Studio for now, so I've gone and put in all the #pragma weak that
the older version supports.

I've checked this into the freedesktop.org git - you can grab the patch
from there and add to builds of our X tree if you want (you'll also need
the previous commit from me in that tree for it to apply cleanly, that
went into nv_61, for which I haven't released the source yet).

The patches are:

#pragma weak:
http://gitweb.freedesktop.org/?p=xorg/lib/libXfont.git;a=commitdiff_plain;h=0fbb37ccc630ced42d6a973c81d947870cca7637;hp=cc824e4f2c9a53a00b36a6f83bf065c363027087

loadable font modules:
http://gitweb.freedesktop.org/?p=xorg/lib/libXfont.git;a=commitdiff_plain;h=cc824e4f2c9a53a00b36a6f83bf065c363027087;hp=fc6e22f238d34918156ded34148730075b7b9cc2

Save them to files in the open-src/lib/libXfont directory, and add the
filenames, followed by ",-p1" to the SOURCE_PATCHES list, so it will
look like:
SOURCE_PATCHES=6206898.patch loadablefonts.patch,-p1 sun-cc-weak.patch,-p1

There's another libXfont fix pending, and then we'll probably roll up a
new release from X.Org with all these fixes later this week.

Unfortunately, my Ferrari 3400 is having a hardware failure, and I need to
reinstall my 4000, so I don't have an machine with ATI graphics handy to
test on - if anyone who has a source tree handy and an ATI machine can
test, that would be good, otherwise I'll have to take apart my current
nvidia test system to swap in the Radeon X300 board.

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering


Reply via email to