Kevin Oberman <oberman(a)es.net> writes in xemacs-beta(a)xemacs.org:
...
> How do you eliminate the myriad of broken preprocessor lines?
The
> gnupg maintainer, evidently, is unwilling to convert them to standard
> C.
On DU the -std1 flag enforces ANSI compliance. -std is ANSI
"with
some relaxations" and it seems to be happy with the pre-processor lines.
Whee. That does the trick.
...
In any case, gnupg-0.9.6 now passes all 23 tests:
Very good.
...
I will attach the diffs for the two files I edited. The edit to
secmem
is clearly a kludge and I need to find the real problem, so I should
have an additional patch before too much longer.
O.K.
I consider the patch to configure to be a fix and don't have any
plan to do anything else to it.
What flavor of ptys are you using? The `expect' binary someone built
here is broken because it assumes the wrong kind, I believe. Perhaps
this is an aspect of the same problem?
The system has no more ptys. Ask your system administrator to create more.
while executing
"spawn ../g10/gpg --no-batch --quick-random --homedir . --gen-key"
FAIL: genkey1024.test
I have `pseudo-device pty 255' in my kernel config file and there
are only a handful of ptys currently in use.
The -lc problem was fixed another way in 0.9.7.