On Wed, Jan 16, 2019 at 7:54 AM Benjamin Kaduk <ka...@mit.edu> wrote: > > On Wed, Jan 16, 2019 at 09:52:26AM -0800, Enji Cooper wrote: > > > > > On Jan 15, 2019, at 5:55 PM, David Cornejo <d...@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
thanks for the responses! Let's say that this might become a port, so I'd create the output files from mkerr.pl by pulling that script from upstream and then include them in the files directory for installation? thanks, dave c -- Kailua, Hawaiʻi US +1 (808) 728-3050 UK +44 (020) 3286 2808 _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
