ccrypt

I just verified that the patch works correctly. Please apply the patch to a
fresh copy of ccrypt-1.9, and not to a previously patched copy.

Hello Maintainer
I tried applying the latest patch. However it told me that they were
already applied. I manually checked the files also. They were already
applied. The makefile.in was also already patched.
bash-2.05$ patch --input myDiff --backup
patching file ChangeLog
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file ChangeLog.rej
patching file configure
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file configure.rej
patching file configure.ac
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file configure.ac.rej

Hi,

yes, you have to re-run automake and autoconf for this patch to take
effect. If this is a problem, you can use the attached
ccrypt-1.9-patch2-ac.diff instead, which also patches the Makefile.in and
configure (you still have to run configure).

The reason you were still unable to build the checks was because your
Makefile wasn't updated.

FYI, the link to "attach a file" is below, past all the comments. -- Peter

Hello Maintainer
I am still unable to build the checks. The undefined entrypoints are still
present. I would like to point out that the following doesnt include the
rjindael-alg-ref.o which contains the rijndaelKeySched, rijndaelEncrypt &
rijndaelDecrypt entrypoints. I am unable to attach my latest buildlog. I
dont see an option for it while adding this comment.
gmake[2]: Entering directory `/<<PATH>>/OpenSource/ccrypt-1.9/check'
gcc -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_SYSV -D_VOS_EXTENDED_NAMES
rijndael-check.c -o rijndael-check
bind: Undefined entry point: rijndaelKeySched, first referenced by
ccQh71nB.
bind: Undefined entry point: xrijndaelKeySched, first referenced by
ccQh71nB.
bind: Undefined entry point: rijndaelEncrypt, first referenced by
ccQh71nB.
bind: Undefined entry point: xrijndaelEncrypt, first referenced by
ccQh71nB.
bind: Undefined entry point: rijndaelDecrypt, first referenced by
ccQh71nB.
bind: Undefined entry point: xrijndaelDecrypt, first referenced by
ccQh71nB.

Thanks
bornlibra23

Thank You Maintainer
I will build it now with the patches applied. Can I ask a question though?
You have made me patch the configure.ac file. Isnt this what is used to
create configure script? Will the system automatically detect that it has
been changed & rebuild configure or I have to manually create the configure
again? I do need autoconf for this dont I?
Thanks
bornlibra23

OK, I have also added a --disable-emacs configuration option for
convenience. For the record, this same behavior can be achieved in
ccrypt-1.9 with "configure EMACS=no".

I have attached a new patch which fixes both the emacs and the test suite
problem.

Thanks for reporting this bug. I am not familiar with Stratus VOS, and this
is the first time I have heard from someone trying to compile ccrypt on it.


(1) Your emacs does not support the -batch command-line option. Either
emacs is not properly installed, or VOS emacs is different than regular
emacs. In either case, you can probably ignore this error. I should
probably add an autoconf test or a --without-emacs configuration option.

(2) Your operating system adds the extension ".pm" to every executable
program, similar to ".exe" in Windows. This breaks the test suite because
after building e.g. rijndael-check.pm, the Makefile then looks for
rijndael-check to run, can't find it, and tries to rebuild it using a
default rule. (For the record, the bug can be reproduced in other operating
systems by doing "make EXEEXT=.pm check".) The attached patch should fix
this problem.

I hope this helps, -- Peter

The program itself works fine through the basic tests I threw at it.