<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: Cipe on SparcLinux?
From: "Les Mikesell" <lesmikesell,AT,home,DOT,com>
Date: Wed, 18 Oct 2000 08:14:07 +0200
In-reply-to: <200010111446.JAA27553@moola.futuresource.com>

----- Original Message ----- 
From: "Olaf Titz" <olaf,AT,bigred,DOT,inka,DOT,de>
To: <cipe-l,AT,inka,DOT,de>
Sent: Monday, October 16, 2000 12:55 PM
Subject: Re: Cipe on SparcLinux?

> > Has anyone compiled cipe under SparcLinux?  I'm
> > getting:
> >
> > .././bf.c:168: conflicting types for `L_Blowfish_Encrypt'
> 
> From which source file? Sparc or Sparc64?
> 
> Try putting #ifdef __KERNEL__ around
> the #include <asm/*> statements in bf.h and put a
> typedef undigned int __u32;
> there.

It is bf.c on a 32-bit sparc (RedHat 6.2 SparcLinux).
I think the real problem is in the expansion of the RoundsP
and RoundP macros.

 .././bf.c:168: conflicting types for `L_Blowfish_Encrypt'
../bf.h:86: previous declaration of `L_Blowfish_Encrypt'
.././bf.c: In function `L_Blowfish_Encrypt':
.././bf.c:169: warning: initialization from incompatible pointer type
.././bf.c:173: invalid operands to binary +
     (repeated 15 more times)
.././bf.c: At top level:
.././bf.c:180: conflicting types for `L_Blowfish_Decrypt'
../bf.h:88: previous declaration of `L_Blowfish_Decrypt'
.././bf.c: In function `L_Blowfish_Decrypt':
.././bf.c:181: warning: initialization from incompatible pointer type
.././bf.c:185: invalid operands to binary +
    (repeated 15 times)

I may never actually need to run CIPE on the Sparc - I just get
nervous about depending on code that won't compile for
other CPU types.

   Les Mikesell
      lesmikesell,AT,home,DOT,com





<< | Thread Index | >> ]    [ << | Date Index | >> ]