On Fri, 12 Nov 2010 10:49:21 +0100
Cedric BAIL wrote:
> On Fri, Nov 12, 2010 at 6:13 AM, Mike Blumenkrantz wrote:
> > Do the eet_data_read/write_cipher calls work? I have been trying to read
> > and write a small amount of data using them and am unable to. The data
> > written is not enciphere
On Fri, Nov 12, 2010 at 6:13 AM, Mike Blumenkrantz wrote:
> Do the eet_data_read/write_cipher calls work? I have been trying to read and
> write a small amount of data using them and am unable to. The data written is
> not enciphered and I cannot read the file back.
It's working for me. What is
Do the eet_data_read/write_cipher calls work? I have been trying to read and
write a small amount of data using them and am unable to. The data written is
not enciphered and I cannot read the file back.
--
Mike Blumenkrantz
Zentific: Our boolean values are huge.
On Fri, 28 May 2004 14:50:17 -0700 Alex Lovell-Troy <[EMAIL PROTECTED]>
(Bbabbled:
(B
(B> -BEGIN PGP SIGNED MESSAGE-
(B> Hash: SHA1
(B>
(B> I'd like to start taking a look at the stuff that will become e17 and
(B> tried to compile from cvs this afternoon 5-28-2004. The libs compil
What version of gcc ?
(from the Embryo README)
WARNING: gcc compatibility!!!
There seems to be some bug (or disagreement) between embryo and gcc 3.2.x
where IEEE floating point format encoding does not "agree" with embryo's own
hand-made tests. embryo_cc may not work if you compile using gcc 3.2.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to start taking a look at the stuff that will become e17 and
tried to compile from cvs this afternoon 5-28-2004. The libs compile
just fine with a slight .libs/.libs problem that manifests itself in
the esmart build. Not a showstopper and
