Commit graph

166282 commits

Author SHA1 Message Date
Austin Seipp 53fb3bb3ef compcert: clean up expression
- Require Coq 8.6.1+
  - Split substituteInPlace call into patchPhase
  - Constrain platforms correctly to x86_64 Linux/Darwin, which was all
it supported anyway (there was no way to properly configure i686 builds,
nor cross builds. In the future there might be)
  - Minor stylistic cleanups
  - Add new 'man' and 'doc' outputs (the previous attempt to move the
build artifact outputs into $lib no longer worked correctly and they
were installed into 'out' instead, this fixes it completely).
  - Clean up weird binary artifacts left in $out (that were already
in $lib)
  - Wrap ccomp to undefine _FORTIFY_SOURCE; otherwise it causes
annoying warnings on every invocation

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-12 20:06:28 -06:00
Vladimír Čunát 570d84a01e
Merge branch 'staging-next' 2019-01-13 00:39:38 +01:00
Jean-Philippe Cugnet 6ca8443c3b scribus: Add an icon (#53456)
* scribus: Add an icon

* scribus: Put the icon SVG in a Gist
2019-01-13 00:01:05 +01:00
Florian Klink 4d9f34a9e6
Merge pull request #53855 from flokli/nextcloud-15.0.2
nextcloud: 15.0.0 -> 15.0.2
2019-01-12 23:04:23 +01:00
Austin Seipp 3d36ea6a05 nextpnr: with GUI support, be sure to set QT_PLUGIN_PATH
This is to help QT find all the necessary plugin libraries at startup
time, otherwise it freaks out when run out of 'nix-env' environment or
run directly, e.g.  `./result/bin/nextpnr-ice40 --gui`. The reason for
this is that none of the traditional paths it looks for are available.
The workarounds for this are to otherwise:

  - Install e.g. into environment.systemPackages (presumably it will
then pick up QT libraries in /run/current-system/sw/lib/qt-*)

  - Install 'qtbase' into your user environment (qt will also try to
load dependent libraries out of ~/.nix-profile/lib/qt-*)

However, this QT_PLUGIN_PATH wrapping hack is used elsewhere in the
tree, presumably to mitigate these (poor) workarounds, especially for
non-NixOS users. There seems to be no downside to this.

With this, I have been able to run NextPNR's GUI on an Ubuntu 16.04
system using the 'nixGL' hack by simply running the resulting binary
from anywhere (though there seems to be some glitching artifacts in the
floorplan UI, I suspect this is due to a buggy OpenGL stack rather than
any direct problem with NextPNR or the QT libraries themselves).

This does not mark the GUI build as non-broken yet, though. That will
happen in the future after a bit more testing and splitting nextpnr into
separate minimal/GUI attributes.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-12 15:51:00 -06:00
Austin Seipp 8b5e6b7711 icestorm: minor cleanup with pythonPkg.interpreter [NFC]
Suggested cleanup by @dotlambda. See:

  18839e1cc1 (commitcomment-31917295)

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-12 15:51:00 -06:00
Florian Klink 58af931a57 nextcloud: 15.0.0 -> 15.0.2 2019-01-12 22:13:23 +01:00
Silvan Mosberger 497e6f1705
Merge pull request #51661 from eonpatapon/testing-hosts
test: set machines fqdn in /etc/hosts
2019-01-12 20:41:13 +01:00
Vincent Laporte ad23ea312d ocamlPackages.lablgtk3: 3.0.β2 → 3.0.β3 2019-01-12 18:42:45 +00:00
Mario Rodas 2c48580be1 flow: 0.89.0 -> 0.90.0 2019-01-12 18:16:28 +00:00
Samuel Dionne-Riel 2646a64fbc
Merge pull request #53827 from samueldr/feature/data-in-logs
tests: Logs timing in tests
2019-01-12 12:54:56 -05:00
Samuel Dionne-Riel 3b68ddb6fe
Merge pull request #53828 from samueldr/feature/double-alarm-time
tests: Wait for shell for twice as long (10m)
2019-01-12 12:08:14 -05:00
Thomas Tuegel 4d2a989b7c
Merge pull request #53846 from NixOS/pr/qt5-darwin-fix
qt5: use 5.11 on darwin until it's fixed
2019-01-12 10:22:35 -06:00
Vladimír Čunát 3131a8ea84
libnice: disable all tests for now :-(
Before this commit it built fine a few times for me,
i.e. without the single test, but it failed on Hydra anyway.
I guess jtojnar also tested the final expression with all tests,
so apparently they are sensitive the the kind of machine they run on.
2019-01-12 17:14:27 +01:00
Will Dietz 7feee4d81f retdec: remove pycache from install dir 2019-01-12 16:48:40 +01:00
Dmitry Kalinkin 37e4390971
qt5: use 5.11 on darwin until it's fixed
Fixes: 8e811ec29 ('qt5: 5.11 -> 5.12')
Resolves: #53841
2019-01-12 09:20:42 -05:00
Timo Kaufmann b54d9e27cb
python.pkgs.pygal: fix build (#53833)
`pytestrunner` is a required build input.

Also we need to explicitly set the locale to pass the tests on darwin.
2019-01-12 15:08:21 +01:00
Robert Schütz baf6252275 python3.pkgs.aiohttp: 3.5.3 -> 3.5.4 2019-01-12 14:56:40 +01:00
Thomas Tuegel b07e1563fe
Merge pull request #53686 from dtzWill/update/poppler-0.73.0
poppler: 0.72.0 -> 0.73.0
2019-01-12 06:50:44 -06:00
Andreas Rammhold 9651cc7a93
Merge pull request #53837 from andir/irssi
irssi: 1.1.1 -> 1.1.2
2019-01-12 13:31:22 +01:00
markuskowa d2e32a22c9
Merge pull request #53173 from r-ryantm/auto-update/unclutter-xfixes
unclutter-xfixes: 1.4 -> 1.5
2019-01-12 13:11:55 +01:00
markuskowa c5bb36f570
Merge pull request #53829 from vbgl/sile-0.9.5
sile: 0.9.4 -> 0.9.5
2019-01-12 13:01:28 +01:00
markuskowa 7fa8e897a5
Merge pull request #53186 from r-ryantm/auto-update/shotcut
shotcut: 18.11.18 -> 18.12.23
2019-01-12 12:52:22 +01:00
Andreas Rammhold 41ee7073df
irssi: 1.1.1 -> 1.1.2
Fixes CVE-2019-5882 [1] and a few minor changes [2].

[1] https://irssi.org/security/html/irssi_sa_2019_01/
[2] https://irssi.org/2019/01/09/irssi-1.1.2-released/
2019-01-12 12:52:16 +01:00
Peter Simons ae56467731
Merge pull request #53810 from NixOS/yegortimoshenko-patch-1
ghc844: update hash for d8495549ba9d194815c2d0eaee6797fc7c00756a patch
2019-01-12 12:31:41 +01:00
Vladimír Čunát bde8efe792
Merge branch 'master' into staging-next
A couple thousand rebuilds have accumulated on master.
2019-01-12 12:19:34 +01:00
Vladimír Čunát 3d73081499
libnice: avoid one test for now
/cc #53293.
2019-01-12 12:11:05 +01:00
Timo Kaufmann 6359e9baf0 python3.pkgs.tinycss: fix build (#53831)
The build was broken by the python 3.7 switch, which caused an
incompatible change in the way cython generates files:

https://github.com/Kozea/tinycss/issues/17

This is solved by removing the pre-generated file and re-generating it
at build time.
2019-01-12 11:24:31 +01:00
Vladimír Čunát 3cd97916fe
xorg xcursor-themes: fix build after #53127 2019-01-12 11:20:43 +01:00
Michael Weiss 768d876394
scons: Remove version 2.5.1 2019-01-12 10:44:33 +01:00
Michael Weiss d8bbec2dff
Merge pull request #53566 from primeos/master
gringo: Switch to the default SCons version
2019-01-12 10:41:39 +01:00
Vincent Laporte 3e7fa939f4
sile: 0.9.4 -> 0.9.5 2019-01-12 10:03:50 +01:00
worldofpeace df712e2055
Merge pull request #53823 from eadwu/vscode/1.30.2
vscode: 1.30.1 -> 1.30.2
2019-01-12 03:27:49 -05:00
Vincent Laporte db217a8aca ocamlPackages.resource-pooling: init at 0.5.2
A library for pooling resources like connections, threads, or similar.

Homepage: https://github.com/ocsigen/resource-pooling
2019-01-12 08:23:48 +00:00
Robert Schütz 98686d3b7f python3.pkgs.aiohttp: 3.5.2 -> 3.5.3 2019-01-12 07:39:28 +01:00
Robert Schütz feae4d6cdb home-assistant: 0.85.0 -> 0.85.1 2019-01-12 07:39:19 +01:00
Samuel Dionne-Riel b28b37eb00 tests: Wait for shell for twice as long (10m)
See #49441 for an earlier attempt, which was subsequently reverted. I am
assuming that doubling the time will be sufficient if the machine is
overloaded since so many of the tests already pass at 5 minutes, while
still not holding back failures for needlessly long.
2019-01-11 22:40:19 -05:00
Samuel Dionne-Riel 5d93e2c01c test-driver: Logs time taken for nests 2019-01-11 22:36:31 -05:00
Samuel Dionne-Riel 1fe0018df8 test-driver: Adds time it took to connect to guest in logs
This will make it possible to track whether the time is generous or not
when ran on hydra.
2019-01-11 22:36:31 -05:00
Dmitry Kalinkin 73625f2522 root5: mark as broken on Linux 2019-01-11 20:45:37 -05:00
Dmitry Kalinkin 0c9335fb1c root, root5: fix build on darwin 2019-01-11 20:45:37 -05:00
Edmund Wu 6b80db3f5f
vscode: 1.30.1 -> 1.30.2 2019-01-11 20:02:00 -05:00
Austin Seipp 61e57a827b icestorm: enableParallelBuilding = true
With the previous PyPy3 change, this reduces the compile time from
~1m30s to roughly 36s (compared to the original, serial, Python 3 build
time of 2:30s).

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-11 18:03:35 -06:00
Austin Seipp 18839e1cc1 icestorm: improve x86 build/runtime perf with pypy
PyPy3 offers tremendous speedups for IceStorm tools written in Python,
including tools used at compile-time to generate the chip databases, and
runtime tools distributed to users, such as icebox_vlog.

For example, on my ThreadRipper 1950X, build times for IceStorm
consistently go from 2m30s -> 1m30s with this change, a 40% improvement,
simply due to improvements in raw CPU efficiency. (This is also worsened
by the fact the build is currently serial, but that can easily be fixed
anyway.)

On top of that, tools distributed to users are also now run using PyPy.
Utilities such as icebox_vlog are useful for post-bitstream testing, for
instance, and also are improved due to improved CPU efficiency as well.
For example, when "decompiling" an ICE40 bitstream for HX8K devices,
containing a synthesized copy of PicoRV32 (from the NextPNR demos), the
runtime of icebox_vlog is cut from 25 seconds to 9 seconds consistently
with this change alone.

Normally, picking a Python interpreter outright for Python-based code is
a "bad idea", but in the case of IceStorm it should be perfectly safe,
and an excellent improvement for users. There are a few reasons for
this:

  - IceStorm uses pure Python 3 and nothing else. There are no
requirements for any 3rd party packages, which might cause annoying
incompatibilities, and PyPy has historically shown very strong core
Python compatibility.

  - IceStorm is NOT a set of Python libraries, it is a set of tools,
some of which, coincidentally, are written in Python. It is (normally)
bad form to fix libraries to certain interpreters versions if the reason
strictly isn't "it doesn't work/isn't compatible". That is not the case
here. These tools may later be used by other programs, such as NextPNR,
but the Python interpreter is ultimately not that important in quesion
for the user. In this sense, there is almost no downside to picking
PyPy explicitly if it offers far better performance.

(Point 2 is not actually strictly true; there are some distributed .py
files that you can import from but they are basically just static
classes that are imported by tools like nextpnr; this is expected.)

Because of this, users should see very little change except better
performance for IceStorm tools on their machines.

Note that PyPy is not supported on aarch64 -- this only applies to
x86_64 machines.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-01-11 18:03:35 -06:00
worldofpeace 9ccd6471b1
Merge pull request #53602 from ivan/wine-4.0-rc5
wine{Unstable,Staging}: 4.0-rc2 -> 4.0-rc5
2019-01-11 18:06:10 -05:00
R. RyanTM a8518f976c yarn: 1.12.3 -> 1.13.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/yarn/versions
2019-01-12 00:00:57 +02:00
worldofpeace 70013f236b
Merge pull request #51236 from fgaz/cht.sh/init
cht-sh: init at unstable-2018-11-02
2019-01-11 15:19:18 -05:00
Vladimír Čunát 414e66f222
boehmgc: avoid mass rebuild due to the parent commit 2019-01-11 20:12:56 +01:00
Dmitry Kalinkin ac7f4c0478
boehmgc: fix patch url
Fixes: 587467a18e ('github-gentoo-compromized_can...')
Closes: #53809
2019-01-11 13:20:05 -05:00
Silvan Mosberger 084e008a2a
Merge pull request #53743 from baracoder/add-nvidia-maintainer
linuxPackages.nvidia_x11*: Add maintainer: baracoder
2019-01-11 19:09:40 +01:00