| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
While here: port related changes:
- Respect PREFIX
- Build a real shared library (with SONAME)
PR: 222483 [1]
Submitted by: takefu@airport.fm [1]
Notes:
svn path=/head/; revision=450903
|
|
|
|
|
|
|
|
|
| |
Using MAKE_ARGS allows building with clang.
Submitted by: bapt
Notes:
svn path=/head/; revision=438117
|
|
|
|
|
|
|
|
|
| |
While here remove useless USES=compiler
Reported by: bapt
Notes:
svn path=/head/; revision=438116
|
|
|
|
|
|
|
|
| |
Now requires GCC. The Clang build is not functional as it fails to link.
The cause is under investigation.
Notes:
svn path=/head/; revision=438115
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Notes:
svn path=/head/; revision=437439
|
|
|
|
|
|
|
| |
Changelog: https://bearssl.org/changelog.html
Notes:
svn path=/head/; revision=431029
|
|
|
|
|
|
|
|
|
|
|
|
| |
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
Notes:
svn path=/head/; revision=426566
|
|
|
|
|
|
|
| |
Reported by: mat
Notes:
svn path=/head/; revision=425321
|
|
|
|
| |
Notes:
svn path=/head/; revision=425239
|
|
in C. It aims at offering the following features:
- Be correct and secure. In particular, insecure protocol versions and
choices of algorithms are not supported, by design; cryptographic
algorithm implementations are constant-time by default.
- Be small, both in RAM and code footprint. For instance, a minimal server
implementation may fit in about 20 kilobytes of compiled code and 25
kilobytes of RAM.
- Be highly portable. BearSSL targets not only "big" operating systems
like Linux and Windows, but also small embedded systems and even special
contexts like bootstrap code.
- Be feature-rich and extensible. SSL/TLS has many defined cipher suites
and extensions; BearSSL should implement most of them, and allow extra
algorithm implementations to be added afterwards, possibly from third
parties.
WWW: https://bearssl.org/
Notes:
svn path=/head/; revision=425235
|