search for: bsdgetopt

...39;-' opt ? optarg (null) ./a.out: invalid option -- 'f' opt ? optarg (null) ./a.out: invalid option -- 'o' opt ? optarg (null) ./a.out: invalid option -- 'o' opt ? optarg (null) whatever it is, I think it's in our compat library: $ nm scp | grep -i getop 08051710 T BSDgetopt -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.

Any ideas of the best way around this problem? Should I just hack the source code, or is there a magic switch somewhere I'm missing? I'm assuming I can't just dismiss that function as OpenSSH is probably based on the OpenBSD semantics. ============================================================================= gcc -g -O2 -Wall -Wno-uninitialized -I. -I.

Hi, I have a problem with the extern declarations of optarg, optind, etc. We're currently moving getopt from being a statically linked function to a dynamically linked function as part of the Cygwin DLL. On Windows, this requires to generate special symbols (__imp__optarg, etc.), which is done by marking the exported variables in the corresponding header. Instead of extern char *optarg;

Hi, The 4.4p1 release is approaching now, so we are now asking people to actively test snapshots or CVS and report back to the mailing list. Snapshots are available from http://www.mindrot.org/openssh_snap or from any of the mirrors listed on http://www.openssh.org/portable.html The latter page also includes instructions for checking out portable OpenSSH via anonymous CVS. This release