Hi all !

I'm currently playing with openssl-0.9.8o to add a cipher in it (just for
fun).

I noticed in crypto/objects that 2 files (obj_dat.h and obj_mac.h) are
automatically generated from scripts which read obj_mac.num and objects.txt.
Therefore I did not update manually obj_dat.h and obj_mac.h.

However, when I run "make" I get errors. Those errors are from obj_dat.h and
obj_mac.h because they were not updated whereas it was supposed to be done
automatically. The scripts didn't run.

For ciphers already included, these errors are not triggered because the
released tarball contains obj_dat.h and obj_mac.h already up-to-date.

The question is, is this a normal behaviour ? In my opinion, it isn't.

Those files aren't updated because they already exist. To build correctly
OpenSSL, I have to rm -f obj_dat.h obj_mac.h. Then when I run "make", the
scripts are executed and those two files are correctly created.

So, if I add a new symetric cipher, to be able to run a correct make test
what would be the right thing to do :
- add the cipher, update those 2 files manually and run config/make/make
test. Therefore, whar's the point of "automatically generated" ?
- add the cipher, run the scripts manually and config/make/make test
- add the cipher, delete those files and config/make/make test.

If it's not either one of those 3 possibilities, then I think there is a
problem. I'd like to have your opinion on this matter.

I hope I made myself clear.

Regards,
Gregory.

Reply via email to