"Arnd Hanses" <[EMAIL PROTECTED]> writes: | Is this bug-bound? Everybody does it (at least in C), I'd say | configure Everybody does not use it...not even in C | is severely broken in too many cases (not only with emx but on systems | like AIX, IRIX, CRAY etc., too). I'd better not trust this problematic | tool; even on Linux I had problems with tests depending in libc4/5. Where/when is configure broken? | >We can have the configure script (or the makefile) setup a link from | >os_specific.h to os2_defines.h, or os_default.h. | | I would like it more to put the actual C++ code into some os_suport.C | and leave the defines in os2_defines.h. I could use then in filetools.C | | #ifdef __EMX__ | #include <os_suport.C> | #endif And then we are back to a multitude of #ifdefs for different systems... Lgb
- 3026 public symbol exports in LyX global name space (w... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Lars Gullik Bjønnes
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Lars Gullik Bjønnes
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Lars Gullik Bjønnes
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Lars Gullik Bjønnes
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Shigeru Miyata
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... miyata
- Re: 3026 public symbol exports in LyX global name... miyata
- Re: 3026 public symbol exports in LyX global ... Lars Gullik Bjønnes
- Re: 3026 public symbol exports in LyX global name... miyata
- Re: 3026 public symbol exports in LyX global name... Arnd Hanses
- Re: 3026 public symbol exports in LyX global name... miyata