| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
This patches go1.6 minimally with a change that was backported
to upstream go1.4.
|
| |
|
|
| |
fixes #23621
|
| | |
|
| | |
|
| |
|
|
| |
The test depends on specific timezone names, and the latest tzdata changed the naming. Upstream only agrees to fix the test in the 1.8 branch that has no stable releases yer
|
| |
|
|
|
| |
In a user namespace, sending credentials for an unmapped user return
EINVAL instead of EPERM. So handle that case.
|
| | |
|
| |
|
|
| |
This has cgo disabled, so only use this for bootstrapping.
|
| |\ |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The go tests get tripped up due to error messages along the lines of:
ld: warning: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation, ignoring unexpected dylib file
Which is due to us passing that along via $NIX_LDFLAGS in the `clang` wrapper.
To keep `go` from getting confused, I create a small `clang` wrapper that
filters out that warning.
Also, the strip.patch is no longer necessary, and only causes problems when
testing DWARF support:
--- FAIL: TestDwarfAranges (0.59s)
runtime-lldb_test.go:218: Missing aranges section
FAIL
FAIL runtime 17.123s
Also, I disable the misc/cgo/errors test, as I suspect it is also due to similar
problems regarding `ld`:
##### ../misc/cgo/errors
misc/cgo/errors/test.bash: BUG: expected error output to contain "err1.go:11:" but saw:
# command-line-arguments
cannot parse gcc output $WORK/command-line-arguments/_obj//_cgo_.o as ELF, Mach-O, PE object
2016/05/07 02:07:58 Failed: exit status 1
Closes #14208
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| | |
See https://github.com/golang/go/issues/14476
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
One of the test scripts dynamically creates and executes a bash script,
which attempts to use `/usr/bin/env bash`. This patches the file to
use the stdenv's shell instead.
Otherwise, the only way this could have worked was by building go_1_6
outside of the sandbox.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
|
| |\| |
|
| | |
| |
| | |
Removed in https://github.com/NixOS/nixpkgs/commit/58dbaf69b7abd7a3483d47bd4eede02d68fcdc78
|
| |/ |
|
| |
|