On Thu, 2001-10-11 at 18:49, D. Stimits wrote: > Murray Cumming wrote: > > > > Part 1.1 Type: Plain Text (text/plain) > > Encoding: 7bit > > Environment variables pass through to Makefile variables. Having > environment variables set to some of the values, whether it is > XERCESCROOT, THREADS, CC, or CXX, means you have done the equivalent of > explicitly naming those values. Having environment variables set means > you have not used a single default setting. To test what I am saying, > one must not have Makefile variables set in the environment.
Yada yada. If I'm not aware of having set any other environment variables, is it likely that I have set any other environment variables? Not only > have I also tested this, others have verified it. Your environment may > be fooling you into believing there is no bug. If you read the mails, you would see that we have all agreed that this *is* a problem when the prefix is not specified. Someone has already posted a partial fix for this. > > D. Stimits, [EMAIL PROTECTED] > > PS: Having XERCESCROOT not default to the root of the tarball unpack, > and having it require manual intervention, is clumsy. It interferes with > clean install of Xerces-c within compound projects. No, it isn't a bug, > but it would be better if a build didn't have to be told where its own > location is in order to build, it could detect this easily enough if not > manually specified. I agree. Do you have a patch to add this behaviour? -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
