| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
64-bit support is only enabled on 64-bit systems
|
| | |
|
| | |
|
| |\
| |
| | |
Various cross-compilation fixes
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
glu: don't use valgrind on darwin
|
| |/ / |
|
| |\ \
| | |
| | | |
kerberos_server: allow choosing MIT or Heimdal
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The intention of the previous change was to move krb5-config to .dev (it
gives the locations of headers), but it grabbed all of the user-facing
binaries too. This puts them back.
|
| | | |
| | |
| | |
| | | |
This contains all of the user binaries as of 13e6a5c.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Leave options for multiple realms for similarity to krb5, and future
expansion. Currently not tested because I can't make it work and don't need
it.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Could also move kdc.conf, but this makes it inconvenient to use command line
utilities with heimdal, as it would require specifying --config-file with every
command.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow switching out kerberos server implementation.
Sharing config is probably sensible, but implementation is different enough to
be worth splitting into two files. Not sure this is the correct way to split an
implementation, but it works for now.
Uses the switch from config.krb5 to select implementation.
|
| | | |
| | |
| | |
| | | |
script causes problems for forking services like MIT Kerberos.
|
| | | |
| | |
| | |
| | | |
General cleanup before adding more options.
|
| | | |
| | |
| | |
| | | |
Don't use socket activation, as inetd is discouraged by heimdal documentation.
|
| | | |
| | |
| | |
| | |
| | | |
tcpd doesn't have sbin anymore (so it was broken), and heimdal just symlinks to
bin.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| | |
Enable autoreconfHook by default: The build tried to execute autoconf, which was
in the wrong build input. Regenerating autotools configure files is always a good
idea since it delivers fixes.
Also move groff to the native since it is only used at build-time
|
| |\ \
| | |
| | | |
radare2: cross-build
|
| | | |
| | |
| | |
| | |
| | | |
Only the make-based build support cross-compilation.
Also use less vendored libraries
|
| |\ \ \
| | | |
| | | | |
iptables: prune libtool files after build
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Otherwise -lpcap gets propagated to reverse deps
This can break strongswan build for example
https://github.com/NixOS/nixpkgs/pull/51252#issuecomment-445512680
|
| |\ \ \ \
| | | | |
| | | | | |
sysvinit: 2.89 -> 2.93
|
| | | | | | |
|
| |\ \ \ \ \
| | |_|/ /
| |/| | | |
glib: fix cross -> inherit devdoc from native build
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Glib uses gobject introspection to generate documentation.
If we would want to cross-compile those, we would need native binaries
from the previous build stage. Instead we can simply just copy over
the generated documentation.
|
| |\| | | |
| |_|/ /
|/| | | |
perl: update perl-cross archive
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
ncurses: fix cross-build by disable stripping
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Ncurses uses `install -s` to also strip the binaries while installing.
This broke the cross build because the wrong strip command was chosen.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
libselinux needs native python to compute the installation prefix.
Swig generates the c code for the extension and needs python.h at compile,
so we put python into buildInputs
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
https://lists.gnu.org/archive/html/info-gnu/2018-12/msg00001.html
|
| |\ \ \ \
| | | | |
| | | | | |
llvm: fix cross-compilation
|
| | | |_|/
| |/| | |
|