| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
| |
together breaks Boost's build scripts.)
|
| | |
|
| |
|
|
|
|
|
| |
This causes packages to have boost.dev in their runtime closures, via
assertion messages.
Fixes #34462.
|
| |
|
|
|
| |
The bootstrap script does not seem to have --without-python; instead
just omit --with-python option
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The reason is that if cross compiling (or for other reasons) python
bindings as a whole are turned off. Those two lines then trigger
assertion errors unless manually overridden for cross compilation.
This way:
1. The `enableNumpy` default respects the `enablePython deafult.
2. Cross works by default
3. Absurd manual overrides still break as they should
4. The `>= 1.65` logic is direct and not a maintaince gotcha.
|
| |\
| |
| | |
boost: Clean, reducing duplication
|
| | |
| |
| |
| |
| |
| | |
This was motivated originally by my cross work, but that goal requires a
few more commits to other things. Still, it's good to start the cleanup
now / get things out of the way.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
In order to manipulate Python arrays numpy is needed from boost 1.65 on.
http://www.boost.org/users/history/version_1_65_1.html
|
| |
|
|
|
|
|
|
|
| |
Certain tools, e.g. compilers, are customarily prefixed with the name of
their target platform so that multiple builds can be used at once
without clobbering each other on the PATH. I was using identifiers named
`prefix` for this purpose, but that conflicts with the standard use of
`prefix` to mean the directory where something is installed. To avoid
conflict and confusion, I renamed those to `targetPrefix`.
|
| | |
|
| |
|
|
|
|
| |
Not built by default.
Also add enablePython flag (enabled by default) and cleanup a bit.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Make either 'bin' or 'out' the first output.
|
| |\
| |
| |
| | |
... to get the ffmpeg changes which cause nontrivial rebuilds.
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
We passed bogus --libdir even in standard native builds;
apparently it wasn't a problem, but I also fixed that.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
- Dynamic linking won't work, it seems.
- When using a native python, the extension isn't built,
so let's not depend on it.
- Replace flags missing on this branch, such as `isCrossWin`.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The upstream sources only compile with masm, so we need to add a patch
that translates the masm sources to GNU assembler. Unfortunately, this
means, that "generic.nix" is no longer very much generic, but the
versions we currently include work fine with the patch.
Unfortunately, the boost build still doesn't finish, but we're getting
there soon enough.
The patch is from https://svn.boost.org/trac/boost/ticket/7262 and
following the discussion it seems that the upstream authors are
unwilling to add a gas version for the Windows platform. So in the long
term we might need to find a better solution to that, like for example
using Wine to run MASM.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |
| |
| |
| |
| |
| |
| | |
I guess the "set -x" was only left there for debugging, so I'm removing
it because it let's the scrollback buffer explode ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |
| |
| |
| |
| |
| |
| | |
Otherwise, Boost.Build is trying to compile against pthread and
desperately searches for icu/iconv.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| | |
| |
| |
| |
| |
| |
| | |
`concatMapStringsSep` actually needs a function to work on the list
items, but it was probably a leftover from the refactor in af8654d.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |/
|
|
|
| |
This was split in somewhere pre-2014 without the current infra which
automates parts of this, in particular the output propagation.
|
| |\
| |
| |
| |
| | |
Beware that stdenv doesn't build. It seems something more will be needed
than just resolution of merge conflicts.
|
| | |\
| | |
| | | |
pkgs.boost: 1.59 -> 1.60
|
| | | |
| | |
| | |
| | | |
See http://www.boost.org/users/history/version_1_60_0.html
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The 'runtime-link=' feature must not be set in addition to 'link='
for boost-1.55 when building only the statically linked libraries.
Fixes errors that targets were defined multiple times.
|
| |\| |
| | |
| | |
| | | |
Let's get rid of those merge conflicts.
|
| | | |
| | |
| | |
| | | |
55 files changed, 6041 deletions. Tested with `nix-build -A tarball`.
|
| |\| | |
|
| | | | |
|
| | |/ |
|
| |\|
| |
| |
| |
| |
| | |
The most complex problems were from dealing with switches reverted in
the meantime (gcc5, gmp6, ncurses6).
It's likely that darwin is (still) broken nontrivially.
|
| | |\ |
|
| | | | |
|
| | |/
| |
| |
| | |
Our higher versions have fix integrated upstream.
|
| | | |
|
| | | |
|