Hi Gregory,
Thus wrote Gregory Bellier (gregory.bell...@gmail.com):
> 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.
I've just had a quick look at 0.9.8k's crypto/objects/Makefile, there's
a dependency between obj_mac.h and objects.txt
obj_mac.h: objects.pl objects.txt obj_mac.num
$(PERL) objects.pl objects.txt obj_mac.num obj_mac.h
Changing one character in objects.txt and calling make in the top-level
directory causes the perl script to run.
What operating system are you using? I recall seeing a problem in this
area on Windows with an mk1mf build where everything is copied into one
large Makefile.
Best regards,
Martin
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
