For the records: That's what the
xserver/xorg/build_NN/mapfile-Xorg-externs actually is, does and how
it gets created:
(I think one of the reasons for its existance is, that a number of
previously stand-alone core modules are now part of (linked into) the
Xorg binary, but ddx modules do depend on their functions.
But Alan can tell you more about the details:
This is what I during the build inside xserver/xorg :
printf '# Functions exported by Xorg server to loadable modules\n\n'
> build_32/mapfile-Xorg-externs
printf '{\n global:\n' >> build_32/mapfile-Xorg-externs
/usr/ccs/bin/nm -g build_32/xorg-server-1.3.0.0/hw/xfree86/Xorg-bin
/media/0A/fox-gate/fox-gate__hg20081025sat/fox-gate/XW_NV/open-src/xserver/xorg/../../../proto-sun4-svr4/usr/X11/lib/X11/xserver/libXfont.so
| grep -v UNDEF | sed -n -e 's/^.*\|FUNC \|GLOB \|.*\|\([A-Za-z].*\)$/
\1 = FUNCTION extern;/p' -e 's/^.*\|OBJT \|GLOB
\|.*\|\([A-Za-z].*\)$/ \1 = DATA extern;/p' >>
build_32/mapfile-Xorg-externs
/usr/ccs/bin/nm: build_32/xorg-server-1.3.0.0/hw/xfree86/Xorg-bin: No
such file or directory
printf '};\n' >> build_32/mapfile-Xorg-externs
--
%martin
