From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003084]: Updated OpenSSL patches to support v0.9.8g
Date: Tue, 22 Apr 2008 21:12:45 -0700 [thread overview]
Message-ID: <eba4f855a2ffcfd67001ee6527ca5ef5@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3084
======================================================================
Reported By: Zero
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3084
Category: Architecture Specific
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-22-2008 21:12 PDT
Last Modified: 04-22-2008 21:12 PDT
======================================================================
Summary: Updated OpenSSL patches to support v0.9.8g
Description:
I have managed to update the OpenSSL patch to work with 0.9.8g.
I have included the patches here. (openssl.mk and openssl.patch).
It might need a little tweaking to work for all users, i cant really say.
Thanks.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
04-22-08 21:12 Zero New Issue
04-22-08 21:12 Zero Status new => assigned
04-22-08 21:12 Zero Assigned To => buildroot
04-22-08 21:12 Zero File Added: OpenSSL patch.tar.gz
======================================================================
reply other threads:[~2008-04-23 4:12 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=eba4f855a2ffcfd67001ee6527ca5ef5@busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.