no // comments, please

Steve VanDevender stevev at darkwing.uoregon.edu
Sat Jun 16 07:49:44 EST 2001


Non-gcc compilers tend not to like C++-style // comments in plain C
code, as I discovered when trying to build the latest snapshot
(20010615) with the Tru64 UNIX C compiler.

*** channels.h.orig     Fri Jun  8 18:20:07 2001
--- channels.h  Fri Jun 15 14:41:01 2001
***************
*** 209,215 ****
  /* x11 forwarding */
  
  int   x11_connect_display(void);
! //int x11_check_cookie(Buffer *b);
  char   *x11_create_display(int screen);
  char   *x11_create_display_inet(int screen, int x11_display_offset);
  void    x11_input_open(int type, int plen, void *ctxt);
--- 209,215 ----
  /* x11 forwarding */
  
  int   x11_connect_display(void);
! /*int x11_check_cookie(Buffer *b);*/
  char   *x11_create_display(int screen);
  char   *x11_create_display_inet(int screen, int x11_display_offset);
  void    x11_input_open(int type, int plen, void *ctxt);

I can also vouch for the problems with building OpenSSH under more
recent Tru64 UNIX versions (I have 4.0G) where -D_SOCKADDR_LEN is
necessary to get the right sockaddr structure defined in sys/socket.h.
What's particularly annoying about this problem is that if you don't
build with -D_SOCKADDR_LEN, the compilation finishes successfully and
you get the rather non-obvious error message "Secure connection to foo
refused" from the ssh binary produced.



More information about the openssh-unix-dev mailing list