Re: [CVS] RPM: rpm/ CHANGES configure.ac rpm/rpmio/ md4.c rmd128.c rmd160....

2007-07-19 Thread Jeff Johnson


On Jul 19, 2007, at 3:40 PM, Jeff Johnson wrote:


Run-time, not compile-time, endian detection please.



Never mind. Those crypto digests are following beecrypt, not rpm,  
programming practice.


So the beecr5ypt programming paradigm is
   #if WORDS_BIGENDIAN

73 de Jeff

__
RPM Package Managerhttp://rpm5.org
Developer Communication Listrpm-devel@rpm5.org


Re: [CVS] RPM: rpm/ CHANGES configure.ac rpm/rpmio/ md4.c rmd128.c rmd160....

2007-07-19 Thread Ralf S. Engelschall
On Thu, Jul 19, 2007, Jeff Johnson wrote:

 On Jul 19, 2007, at 3:40 PM, Jeff Johnson wrote:

 Run-time, not compile-time, endian detection please.

 Never mind. Those crypto digests are following beecrypt, not rpm,
 programming practice.

 So the beecr5ypt programming paradigm is
#if WORDS_BIGENDIAN

Yes, I know. I've explicitly checked beforehand from where
WORDS_BIGENDIAN came and have seen that is an Autoconf check present in
BeeCrypt's configure but which was missing on our side. As a side-effect
our side was broken although the code itself followed just fine the
BeeCrypt coding practice. But as it is compiled outside the BeeCrypt
build environment we have to provide the missing pieces ourself...

   Ralf S. Engelschall
   [EMAIL PROTECTED]
   www.engelschall.com

__
RPM Package Managerhttp://rpm5.org
Developer Communication Listrpm-devel@rpm5.org


Re: [CVS] RPM: rpm/ CHANGES configure.ac rpm/rpmio/ md4.c rmd128.c rmd160....

2007-07-19 Thread Jeff Johnson


On Jul 19, 2007, at 3:50 PM, Ralf S. Engelschall wrote:


On Thu, Jul 19, 2007, Jeff Johnson wrote:


On Jul 19, 2007, at 3:40 PM, Jeff Johnson wrote:


Run-time, not compile-time, endian detection please.


Never mind. Those crypto digests are following beecrypt, not rpm,
programming practice.

So the beecr5ypt programming paradigm is
   #if WORDS_BIGENDIAN


Yes, I know. I've explicitly checked beforehand from where
WORDS_BIGENDIAN came and have seen that is an Autoconf check  
present in
BeeCrypt's configure but which was missing on our side. As a side- 
effect

our side was broken although the code itself followed just fine the
BeeCrypt coding practice. But as it is compiled outside the BeeCrypt
build environment we have to provide the missing pieces ourself...



Ah, like missing HAVE_MMAP. My apologies for the noise.

How do you notice these things btw? ;-)

73 de Jeff
__
RPM Package Managerhttp://rpm5.org
Developer Communication Listrpm-devel@rpm5.org