On Mon, Jan 13, 2003 at 12:16:48PM -0500, Mike A. Harris scrawled: > I have also had a problem with trying to use the HasExpat > directive in host.def. > > If I define HasExpat to YES in the host.def, then the build fails > early on trying to go into ../usr/lib//usr/lib or some similar > weirdness. > > I talked to Keith Packard about it a month ago or so and he > helped me to try and figure out the problem, however was unable > to reproduce it himself. I suspect that our two setups are > probably different in some way. I did find a craptastic > workaroudn though. I don't define HasExpat, but I let it build > it anyway, then just don't use it. That works for me ok. > > I've seen users of other distros and OS's report this too in IRC > and I've given them my workaround. > > Daniel Stone, in Debian I believe has come up with a different > workaround and perhaps even a proper fix, however I forgot about > the discussion going on about this problem and lost it. Perhaps > if he's reading this he can comment too.
I just #define HasExpat YES, which works for me. The pain in the arse I had was that we have Expat includes in /usr/include (sigh), which meant it was pulling in -I/usr/include. Which is bad if you have stale X headers kicking around, and no package should ever Build-Conflict on itself. My even more craptastic solution was to excise -I$(EXPATINCDIR) from CFLAGS. UGH. -- Daniel Stone <[EMAIL PROTECTED]> Developer, Trinity College, University of Melbourne
msg00241/pgp00000.pgp
Description: PGP signature
