RE: misc/23729 (please add a FAQ on the 'Syntax error: "(" unexpected' ld.so issue)

[<refling%alumni.stanford.edu@localhost>]

The following reply was made to PR misc/23729; it has been noted by GNATS.

From: <refling%alumni.stanford.edu@localhost>
To: <gnats-bugs%netbsd.org@localhost>
Cc: 
Subject: RE: misc/23729 (please add a FAQ on the 'Syntax error: "(" unexpected' ld.so issue)
Date: Fri, 17 Jun 2022 13:28:18 -0700

 Yes, probably time to close it.
 
 John Refling 
 
 -----Original Message-----
 From: matthew green [mailto:mrg%eterna.com.au@localhost] 
 Sent: Thursday, June 16, 2022 10:45 PM
 To: misc-bug-people%netbsd.org@localhost; gnats-admin%netbsd.org@localhost;
 netbsd-bugs%netbsd.org@localhost; refling%acm.org@localhost
 Subject: re: misc/23729 (please add a FAQ on the 'Syntax error: "("
 unexpected' ld.so issue)
 
 The following reply was made to PR misc/23729; it has been noted by GNATS.
 
 From: matthew green <mrg%eterna.com.au@localhost>
 To: gnats-bugs%netbsd.org@localhost
 Cc: misc-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
     gnats-admin%netbsd.org@localhost, kre%NetBSD.org@localhost, refling%acm.org@localhost
 Subject: re: misc/23729 (please add a FAQ on the 'Syntax error: "("
 unexpected' ld.so issue)
 Date: Fri, 17 Jun 2022 15:40:21 +1000
 
  > Can we close this PR?
  
  at least for sh, i think it's resolved due to:
  
  > Also, /bin/sh now does a check for exec'ing ELF format files, and no  >
 longer tries to run them as scripts, when the simple exec fails (if you  >
 ask to run it as a script "sh file" then it will attempt it of course).
  
  
  > Not sure about /bin/ksh - but as long as the kernel is returning ENOENT
 > in the case in question, it also doesn't have the problem reported.
  
  ksh is fun :)
  
  space-bird ~> /bin/sh /bin/sh
  /bin/sh: Cannot execute ELF binary /bin/sh  space-bird ~> /bin/ksh /bin/ksh
  /bin/ksh[1]: syntax error: `QX^F^DFC#*U^M' unexpected
  /bin/ksh[1]:
  space-bird ~> /bin/ksh /bin/sh
  /bin/sh[3]: syntax error: `(' unexpected
  /bin/sh[3]:
  
  csh and tcsh are even more fun.  the different is related to  the 2nd arg
 (similar output depending on the input.)
  
  space-bird ~> /bin/csh /bin/csh
  ^F^D@@@M-@^AM-@^A^H^C^D^B^B^B^S^S^A^A^EM-4B^BM-4B^B: Event not found.
  
  space-bird ~> /bin/tcsh /bin/tcsh
  ^?ELF^B^A^A^B: Command not found.
  Missing }.
  Missing }.
  H\205\377^O\204^]^AL\215\255\220\376\377\377\350F^^^DI\211\304L\211\356H\2=
  11\307\350\210\343: Command not found.
  [1] 12918
  \2441H\213E\310H+^E^S\3052^O\205/^BH\201\304h^A[AA]A^A_]\303L\211\346\277:=
   No match.
  Illegal variable name.
  \202u3E1\377H9\312A^O\237\307\213\205\230\376\377\377%\360=3D@^O\204\367H\=
  203\275\377\377\377^O\204\250H\213\205\300\376\377\377H9\302^O\216\230H\21=
  35\325\2441H9\360^?: Command not found.
  Missing }.
  H\205\377^O\205\361\376\377\377H\213\225\210\376\377\377H\211^U: Command n=
 ot found.
  
  
  .mrg.