Hi Andy,
We have standards for the compilers that we use on each platform, and on
Windows it is Microsoft's toolset. In our lab we use cygwin for the build
framework so that we can use the same framework on Windows and Unix
platforms.
What I was trying to say was that rather than using the .bat
I have one other issue I need resolution on: when I run the make file
under cygwin, the resulting libraries are exactly what I get on unix:
libssl.a and libcrypto.a. What I want to know is how do I get
ssleay32.dll and libeay32.dll? These are required to link m2crypto on
Win32.
Mark
On May
Steven,
I've written a command-line utility called gcc2cl which acts like a gcc
front-end while using Microsoft's compiler/linker at the backend. It
translates options and does some munging of cl's stdout/stderr so as to fool
autoconf into thinking it is really using gcc. This enables us (I did
Andy Polyakov wrote:
Steven,
I've written a command-line utility called gcc2cl which acts like a gcc
front-end while using Microsoft's compiler/linker at the backend. It
translates options and does some munging of cl's stdout/stderr so as
to fool
autoconf into thinking it is really using gcc.
Mark,
When I get time I'll clean up the implementation and post the source to this
list. In the meantime I'll send you the binary tomorrow when I'm at work.
Regards,
Steven
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Mark Jaffe
Sent: Monday, 10
As we all know excludes me so I talked to one of our experts here to
find out the answer to your questions. This was his response:
[Embedded Response]
NetWare supports SSE2 up to a point. NetWare assumes that the XMM
registers are scratch registers across procedure calls. NetWare
preserves the
The libssl.a and libcrypto.a binaries are linked to cygwin1.dll. This
is not what you want.
You do not want to be using the cygwin build process but the MS Visual
Studio build environment.
Perhaps you can use the cygwin environment to kick off a normal OpenSSL
build in the background.
Jeffrey
Exactly what I want to do, but we need a little customization. That's
where I ran into problems. Steven Reddie seems to have a solution, hope
it works for us.
Mark
On May 10, 2004, at 6:06 PM, Jeffrey Altman wrote:
The libssl.a and libcrypto.a binaries are linked to cygwin1.dll. This
is
Jeffrey,
Are you saying that using something like gcc2cl to kick off a build the way
you do for cygwin, but using the Microsoft compiler, is the wrong way to go?
It's working well for us in-house, though we've been using static libraries
up until now and are just finishing up changes to support
Since the cygwin environment is different from the MS Run Time
environment, I would not make the assumption that the binaries
produced use exactly the same configuration options. They may
but I would not count on it.
I understand what you are attempting to do; I just do not know if
the results
Ok, I understand where you're coming from. What we have works fine, through
we've not played around with Kerberos. I've created a new CygwinMSVC
entry in Configure which uses enough of the Cygwin entry to integrate with
the rest of the build framework, but uses a SYSNAME of WIN32 (not CYGWIN32)
I receive one of the following for every message I send to the list.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, 11 May 2004 2:08 PM
To: Steven Reddie
Subject: Mail Returned (550 5.1.1 [EMAIL PROTECTED]... User unknown
(RCPT))
Your mail was
12 matches
Mail list logo
