From: mutazilah@gmail.com   
      
   On 21/02/24 11:36, Peter 'Shaggy' Haywood wrote:   
      
   >> b) accept your request and add an O_TEXT flag that does nothing, or   
   >>   
   >> Choice (b) is ... useless. It recognizes a non-issue, and does   
   >> nothing. It would be a header change that reserves a flag that would   
   >> be ignored by everyone. I believe that the maintainers would simply   
   >> veto this as being a change that makes no change.   
   >   
   >   This would be useless, true. But it would be harmless. It could be   
   > defined simply as   
   >   
   > #define O_TEXT 0   
      
   No. It can't be that. It needs to be non-zero so   
   that I can detect it in a non-Linux environment.   
      
   >   I think what the OP is proposing is option (b) above: allow an O_TEXT   
   > identifier having no effect.   
      
   No effect ... on Linux.   
      
   An effect ... on PDOS/386.   
      
   >   To the OP: a solution to your problem is simple. Put the following   
   > lines in your source code before any use of O_TEXT:   
   >   
   > #ifndef O_TEXT   
   > #define O_TEXT 0   
   > #endif   
      
   No, that doesn't solve my problem.   
      
   When the ELF executable is run on PDOS/386, I will   
   have no way of knowing that this open is text, and   
   thus PDOS/386 (the OS) should add CRs whenever it   
   sees a LF.   
      
   Because we're beyond the point when anyone else   
   would add the CR.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)