* Compile with gcc5 to avoid the compiler bug described in
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02560.html
* Add a patch to fix the many incorrect printf format specifiers and
other sloppy type conversions that gcc5 catches and warns on
(erroring out due to -Werror).
In 4.1, the build system changed, and it now wants to execute ld like this:
ld -r -o util/scripting-engines/libperf-in.o util/scripting-engines/trace-event-perl.o util/scripting-engines/trace-event-python.o
The actual problem seems to be that `buildInputs = [elfutils ...]`
causes 'ld' to point to elfutils in PATH instead of the usual binutils.
So remove elfutils from buildInputs and set NIX_CFLAGS_* manually. This
is a slight hack, but there is some precedent:
0761f81da7/pkgs/tools/package-management/rpm/default.nix (L13)Fixes#9095.
Or else users may see this unfriendly message:
error: cannot coerce null to a string, at .../nixos/modules/services/x11/display-managers/gdm.nix:107:49
Second attempt to resolve this issue. Copies stage1 image into expected
place manually. This has been improved in rkt master where there is a
configure option for specifying the location of this file. Can update
when next stable rkt is released.
Local build and run successful.
From the ChangeLog:
```
Version 0.7.77, 2015-09-02
+ #B941, MXF: files having only a video stream and an ancillary data
stream were having incorrect second video stream
+ MOV: detection of r210 CodecID as raw RGB
+ Ancillary data: detection of all metadata blocks (previously: only the
first one was detected)
x MPEG-TS: Wrong demux of TSP (188+16 TS) files having PES with only
padding x MediaTrace #2: XML malformed with Flags items (hotfix, flags
meaning disabled in XML output)
x MediaTrace #3: XML malformed with some MP4 files
x MediaTrace #6: XML duplicated attributes
x MediaTrace #10: versioned xsd, creating library name and version
x MediaTrace: XML content was not escaped
x #B947, Amazon S3 support (REST API v2), CLI/DLL only and if compiled
with libcurl support: Analyze file on s3 was not working if secret key
contains / character
```
