Cardano Updates

Signed-off-by: yHSJ <[email protected]>

reviewed and selected trace Options all-in-one for relay and producer nodes.
maxFrequency settings prevent spaming the logs.
MachineFormat writes the logs in json and makes it readable for both humans and monitoring tools

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

* Update nixpkgs-unstable and nixpkgs-2511, fix deprecation warnings

Update nixpkgs-unstable and nixpkgs-2511 pins and fix the resulting
evaluation warnings for deprecated package names. Uses
backwards-compatible fallback patterns so older nixpkgs still works:

- Replace xorg.* references with (pkgs.newName or pkgs.xorg.oldName)
- Add xorgCompat set in pkgconf-nixpkgs-map.nix to map deprecated
  xorg attribute names to their new top-level equivalents
- Update renamed packages (enchant2, unixODBC, goocanvas, etc.)
  using a prefer helper that selects the new name when available

* Patch hp2ps for GCC 15 compatibility (GHC 9.6–9.8)

GHC 9.6.x and 9.8.x utils/hp2ps/Utilities.c uses K&R-style
extern declarations for malloc/realloc without including <stdlib.h>.
GCC 15 treats these as zero-argument functions, causing build failure.

* Remove deprecated 'pie' hardening flag for musl builds

nixpkgs 26.05 removed 'pie' from the hardening system entirely -- PIE
is now enabled by default in compilers. Any mention of 'pie' in either
hardeningEnable or hardeningDisable triggers a deprecation warning:

  "The 'pie' hardening flag has been removed in favor of enabling PIE
   by default in compilers and should no longer be used."

This causes ~68 warnings per evaluation for projects with musl
cross-compilation, which is every haskell.nix project using
crossPlatforms with musl64 or aarch64-multiplatform-musl.

Remove the two places where 'pie' was added to hardeningDisable:
- builder/comp-builder.nix: every Haskell component on musl
- compiler/ghc/default.nix: GHC itself on musl targets

* Make pie hardening removal backwards compatible

Only disable pie for musl when the toolchain still has it as a
default hardening flag (nixpkgs <= 25.05). On newer nixpkgs where
pie was removed from the hardening system, skip it to avoid the
deprecation warning.

* Add wine 11.0 patch for LdrAddDllDirectory device paths

Wine 11.0 renamed DOS_PATHNAME_TYPE to RTL_PATH_TYPE and changed
the enum values (DEVICE_PATH -> RtlPathTypeLocalDevice). Add a
new patch variant for wine >= 11.0 that uses the new API names.

* Drop removed 'static' argument from zlib override in android overlay

The 'static' parameter was removed from zlib in nixpkgs-unstable.
Setting 'shared = false' is sufficient to get a static-only build
and works across all nixpkgs versions.

* Fix emnm path for emscripten 4.0+ in GHCJS builds

Emscripten 4.0+ moved emnm from share/emscripten/emnm to
share/emscripten/tools/emnm.py. Use builtins.pathExists to
select the correct path for backwards compatibility.

* Fix musl cross-compilation for libffi, gmp and ncurses

- libffi, gmp: disable doCheck when cross-compiling since test
  binaries can't execute on the build host
- ncurses: disable broken symlink check when cross-compiling to
  avoid case-sensitive symlink target mismatch

* Disable terminfo for cross-compilation, fix ncurses handling

Hadrian builds terminfo unconditionally for stage0, passing the same
--with-curses-libraries to both stage0 (host compiler) and stage1
(target compiler). Before GHC 9.15 (which has MR 13932), this cannot
work when the host and target have different ncurses (e.g. glibc vs
musl), because the host compiler can't link against target static libs.

Matching nixpkgs common-hadrian.nix:
- Disable enableTerminfo when platform configs differ (cross builds)
  for GHC < 9.15
- Gate --with-curses-libraries on enableTerminfo so it's not passed
  in cross builds (avoiding the stage0 ABI mismatch)
- Keep ncurses in libDeps unconditionally (not gated on enableTerminfo)
  since hadrian builds terminfo for stage0 regardless, and
  depsTargetTarget needs target ncurses for stage1

* Extend hp2ps stdlib patch to all affected GHC versions

The K&R-style extern void* malloc() in utils/hp2ps/Utilities.c
is present in all GHC versions from 8.10.7 through 9.12.3.
It was fixed with a proper prototype in 9.10.2 and fully fixed
with #include <stdlib.h> in 9.10.3 and 9.12.4+.

* Fix Wine for 11.0+: use lib.getExe and wine64Packages

Wine 11.0 removed the wine64 binary, unifying it into wine.
Use wine64Packages.minimal (for 64-bit support) and lib.getExe
to pick the correct binary name via meta.mainProgram.
Also patch wine64Packages.minimal with the same fixes as
winePackages.minimal.

* Skip lit max-time.py self-test in wasm LLVM build

Test hangs in the nix build sandbox: a Python multiprocessing.Pool
deadlock (`_help_stuff_finish` acquires `inqueue._rlock` without
releasing) combined with a leaked signal mask that leaves SIGTERM
blocked in the worker means `pool.terminate()` can't kill it.
nix-shell builds complete fine; only nix-build hangs.

---------

Co-authored-by: Mateusz Galazyn <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Signed-off-by: Doc Holiday <[email protected]>

Names like `SERVER_URL` are pretty generic – let’s prevent accidental
clashes from inherited env.

The new deployment at <https://icebreakers.mainnet.core.blockfrost.io/>
is not using them, so we’re safe to do it.

Add 'targetBytesSize :: BytesSize' parameter to 'choosePeerTx' and
replace the 'not $ Map.null txOffsets'' guard with a check that an
arbitrary entry in 'txOffsets'' claims the same size, per
@nfrisby's review.

An honest peer wouldn't offer EbClosures for EBs that assign
different sizes to the same tx, so every entry in 'txOffsets'' has
the same size and a single-entry check is representative. For an
adversarial peer it's inevitable that they could send a different
amount of bytes than requested, so the accuracy of
'requestedBytesSize' and 'requestedBytesSizePerPeer' is not
particularly important or achievable — the single-entry check is
sufficient.

Addresses @nfrisby's review comment.

Agent-Logs-Url: https://github.com/blinklabs-io/dingo/sessions/add57770-2192-4b38-93fc-81a3d3dcc7ca

Co-authored-by: wolf31o2 <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Agent-Logs-Url: https://github.com/blinklabs-io/dingo/sessions/add57770-2192-4b38-93fc-81a3d3dcc7ca

Co-authored-by: wolf31o2 <[email protected]>