Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: ec1c8071b1a44c623aa83a3edcaf71562957290b
      
https://github.com/NixOS/nixpkgs/commit/ec1c8071b1a44c623aa83a3edcaf71562957290b
  Author: Charles Strahan <[email protected]>
  Date:   2016-05-06 (Fri, 06 May 2016)

  Changed paths:
    M pkgs/applications/editors/vim/macvim.nix
    M pkgs/top-level/all-packages.nix

  Log Message:
  -----------
  macvim: fix build


  Commit: e965e42dc5946b8988045ac2ca8f7dfe3f4e6ce4
      
https://github.com/NixOS/nixpkgs/commit/e965e42dc5946b8988045ac2ca8f7dfe3f4e6ce4
  Author: Charles Strahan <[email protected]>
  Date:   2016-05-06 (Fri, 06 May 2016)

  Changed paths:
    M pkgs/development/compilers/go/1.6.nix

  Log Message:
  -----------
  go: fix build on Darwin

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


Compare: https://github.com/NixOS/nixpkgs/compare/c083ef0c6d67...e965e42dc594
_______________________________________________
nix-commits mailing list
[email protected]
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Reply via email to