WinCE is no longer supported.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3498
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
> -Original Message-
> From: owner-openssl-...@openssl.org [mailto:owner-openssl-
> d...@openssl.org] On Behalf Of Pierre DELAAGE
> Sent: Thursday, August 21, 2014 6:05 AM
> To: openssl-dev@openssl.org
>
Hi all,
I just wanted to state the fact, that we maintain openssl for os/2 also
on a seperate svn, as we did include some fixes which are not in the
openssl trunk.
We would like to have them in the trunk, but we always thought no one
could even look at them.
And of course removing all os/2 stu
> Did I miss something, or did you happen to count the includes of "e_os2.h"
> which is not OS/2 specific at all? Or both?
No, I made the stupid mistake.
> The current version of eComStation, 2.1, was released only a year
> after version 2.0, in May 2011.
We were not aware of eComStation. Thank
Hi,
> There are 70 files that have OS2 in them, for a total of 130 instances.
Strange. Here, I obtain:
> grep -r OS2 * | wc -l
52
> grep -r OS2 * | sed "s/\([^:]*\)\:.*/\1/" | uniq | wc -l
22
i.e. 22 files with a total of 52 instances.
Did I miss something, or did you happen to count the
Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
> -Original Message-
> From: owner-openssl-...@openssl.org [mailto:owner-openssl-
> d...@openssl.org] On Behalf Of Pierre DELAAGE
> Sent: Thursday, August 21, 2014 6:05 AM
> To: openssl-dev@openssl.org
>
On Wed, Aug 20, 2014 at 10:12 AM, Salz, Rich wrote:
>> Minor clarification is appropriate. MSDOS is supported in single "stance",
>> namely DJGPP, which is 32-bit environment.
>
> Good point.
>
> So the idea is that MSDOS gets turned into DJGPP. BEOS and OS/2 are removed
> in HEAD (i.e., after 1
Dear All,
At least for WCE, I can say that with this patch:
https://www.mail-archive.com/openssl-dev@openssl.org/msg35958.html
which is W32 compatible and NOT WCE specific,
and consists of only one typedef (which is highly clarifying the code
ALSO for win32) and one CAST error (cast error that S
Thanks for the feedback!
There are 70 files that have OS2 in them, for a total of 130 instances. That's
rather a lot for a platform that hasn't had an update in five years.
This is my personal opinion, as a team member. We will release 1.0.2 this
year. At that time we will announce end of li
> Does anyone want to speak up for the requirement that we continue to support
> BEOS (apparently B/1 and R5?), OS/2, or pre-Windows MSDOS?
Which timeframe do we look at? E.g. if 1.0.2 is released this year and it's
successor
where OS/2 support is removed maybe 2-3 years later (say beginning
I'm not sure what WINDOWS means. And I'm not sure MSFT knows either :)
Less flippantly, the goal is that OPENSSL_SYS_WINDOWS means any Windows
platform, and then there are subtypes within that. We'll figure it out as we
go along. It's gonna take a while to clean up the #ifdef world without
b
> Minor clarification is appropriate. MSDOS is supported in single "stance",
> namely DJGPP, which is 32-bit environment.
Good point.
So the idea is that MSDOS gets turned into DJGPP. BEOS and OS/2 are removed in
HEAD (i.e., after 1.0.2), and Microsoft means WINDOWS of various flavors.
If this
> Does anyone want to speak up for the requirement that we continue to
> support BEOS (apparently B/1 and R5?), OS/2, or pre-Windows MSDOS?
Minor clarification is appropriate. MSDOS is supported in single
"stance", namely DJGPP, which is 32-bit environment. 16-bit code was
never supported by OpenS
Does anyone want to speak up for the requirement that we continue to support
BEOS (apparently B/1 and R5?), OS/2, or pre-Windows MSDOS?
Unless there is strong interest and commitment, we will drop these after 1.0.2
/r$
--
Principal Security Engineer
Akamai Technologies, Cambridg
14 matches
Mail list logo
