From: "Prentis Brooks" <prentis@aol.net>
To: "Cygwin" <cygwin@sourceware.cygnus.com>
Subject: OpenSSL still won't compile
Date: Wed, 31 May 2000 13:54:00 -0000 [thread overview]
Message-ID: <NEBBLEPLMLJEEFHAGMDMEECPCAAA.prentis@aol.net> (raw)
Ok... I have applied the patch to patch, then untarred the openssl source
and repatched it with the new patch. Double checked files to ensure there
were no ^M's in the file, it is clean. Then attempted to run configure.
Tried the following two commands (the first being the desired):
./Configure CygWin32 --prefix=/usr/local -no_idea rsaref
and
./Configure CygWin32 --prefix=/usr/local
(Also tried commands with CygWin32 at the end, just in case that made a
diff, it did not).
For both I got the same result, the result I had before I applied the patch
to patch:
Makefile.ssl:155: *** commands commence before first target. Stop.
Any other ideas?
Prentis...
(Note, I would check the archives if I had any other ideas as to where or
what to look for)
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
reply other threads:[~2000-05-31 13:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NEBBLEPLMLJEEFHAGMDMEECPCAAA.prentis@aol.net \
--to=prentis@aol.net \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).