Date: Wed, 16 Jan 2019 11:54:44 -0600 From: Benjamin Kaduk <kaduk@mit.edu> To: Enji Cooper <yaneurabeya@gmail.com> Cc: David Cornejo <dave@dogwood.com>, FreeBSD Current <freebsd-current@freebsd.org>, Jung-uk Kim <jkim@freebsd.org> Subject: Re: openssl 1.1.1 utils mkerr.pl Message-ID: <20190116175444.GH91727@kduck.mit.edu> In-Reply-To: <0FD8FC97-BE08-41E2-A414-87991B9B5180@gmail.com> References: <CAFnjQbuaHeFRCPxLDc3sKC5Trh1Utio=rX4Q0VDa3uEYm5cwxA@mail.gmail.com> <0FD8FC97-BE08-41E2-A414-87991B9B5180@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 16, 2019 at 09:52:26AM -0800, Enji Cooper wrote: > > > On Jan 15, 2019, at 5:55 PM, David Cornejo <dave@dogwood.com> wrote: > > > > Hi, > > > > I am working on some code that wants to use mkerr.pl from the openssl > > distribution - but this appears to have been left out of the import to > > base. > > > > Is there an alternative method to create the include files produced > > from this script in FreeBSD? > > > Hi Dave, > > I would go a different route from what was mentioned by others — I would > actually either grab mkerr.pl from upstream from the release package > (upstream on GitHub is https://github.com/openssl/openssl/releases ) > (sidenote: I don’t know why, but our vendor-crypto tree lacks this script > as well; jkim@ CCed). Why go this route? You can easily grab the file The script is used by upstream when preparing a release; we only use the finished release objects from upstream and do not expect to be doing this sort of "pre-release" step in our own operations. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190116175444.GH91727>