Herbert, Let me know if you did not get the attachment.
-----Original Message----- From: Steele, Raymond Sent: Monday, December 02, 2013 3:29 PM To: 'Herbert Duerr'; [email protected] Cc: Meffe, David K Subject: RE: EXTERNAL: Re: Building comphelper Herbert, We are having trouble interpreting the boost preprocessor macros. We are receiving the following output when compiling sal/osl/all. I've attached the output as a pdf. Raymond -----Original Message----- From: Herbert Duerr [mailto:[email protected]] Sent: Friday, November 22, 2013 2:14 AM To: [email protected] Cc: Steele, Raymond; Meffe, David K Subject: Re: EXTERNAL: Re: Building comphelper Hi Raymond, On 21.11.2013 22:27, Steele, Raymond wrote: > Forget about my last report. We started over and figured out that an > environment variable was causing the dmake issues. Once we cleared the > environment of variables related to our other projects, the build took off. > We will have to figure out what it was later. Thanks for debugging and solving that problem! The current way of configure writing a file for setting environments variables is too fragile. As can be seen in your example if configure is run in an environment that is already "contaminated" with such env vars then unnecessary causes of troubles exist. IMHO build and config settings should be done via e.g. Makefile.config that should be created by configure. This config result should then be included by the other Makefiles. So if in doubt better use a fresh shell before running configure. Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
