--pgp-sign-Multipart_Sat_Aug__5_16:44:51_2006-1
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

At Sun, 30 Jul 2006 12:04:51 +0200,
Julio M. Merino Vidal wrote:
>=20
> You are right in that there is a problem, but there is no build error
> (hence why it went unnoticed for so long).  The problem only appears
> at run time with a warning message that I had not noticed until now:
>=20
> Symbol xf86LoadVBEModule from module
> /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved!

Well the build does fail immediately if one links with -static.  ;-)

That's one, albiet relatively minor, reason why I do like to link
everything statically for my systems.

Until the dynamic linker is fixed to have an option to force it to fail
if any symbol remains undefined (or there are other potential load-time
problems, such as multiple definitions, etc.) then I think it would be
very wise for someone other than myself (perhaps even the automated
builds) to do at least one complete static-linked build for at least
some architectures.


> The fix is trivial: just revert the offending line to what it was (a
> call to xf86LoadSubModule).  I'm now testing the fix locally
> (attached).

Thanks very much!  All seems OK with static xsrc-current builds on 1.6.x
now (though I don't think I have any hardware to test if the module
acutally works).

--=20
						Greg A. Woods

H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>       Secrets of the Weird <woods@weird.com>

--pgp-sign-Multipart_Sat_Aug__5_16:44:51_2006-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: oZjULcD6XF5kvp6NzFAPC27/Q613ovPT

iQA/AwUBRNUDRmJ7XxTCWceFEQJqMwCgprewKHn2IFz2oOsXsV64R896/4AAnAzu
nfx097vFZgBPxvUJVi0nUk3d
=dO85
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Sat_Aug__5_16:44:51_2006-1--