| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
|
|
|
|
|
|
|
| |
With minor cleanups to make things simpler.
With hat: portmgr
Sponsored by: Absolight
|
| |
|
|
|
|
| |
Approved by: just fix it
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
| |
*.efi files as executables; from the strip(1) point of view they are data
files (actually, they are executables, but PE, not ELF).
Sponsored by: The FreeBSD Foundation
|
|
shim is a trivial EFI application that, when run, attempts to open and
execute another application. It will initially attempt to do this via the
standard EFI LoadImage() and StartImage() calls. If these fail (because secure
boot is enabled and the binary is not signed with an appropriate key, for
instance) it will then validate the binary against a built-in certificate. If
this succeeds and if the binary or signing key are not blacklisted then shim
will relocate and execute the binary.
Sponsored by: The FreeBSD Foundation
|