Packaging/32bit Applications - Revision history

Sewer56: Added Rust and LTO Cross Compile Notes

2025-12-13T18:01:37Z

Added Rust and LTO Cross Compile Notes

← Older revision		Revision as of 18:01, 13 December 2025
Line 27:		Line 27:

	You will want something similar to the following in your <code>flake.nix</code>, <code>devenv.sh</code> , or whatever you're using as your entry point.		You will want something similar to the following in your <code>flake.nix</code>, <code>devenv.sh</code> , or whatever you're using as your entry point.

			==== Rust LTO & cargo bench ====
			If you are using LTO and are having trouble building benchmarks (<code>cargo bench</code>) you may need to disable it at the build step until someone documents a better workaround here.<syntaxhighlight lang="nix">
			env = {
			# Disable LTO for C/C++ code compiled by the `cc` crate for i686.
			# Some crates (like `alloca`) add -flto when CC=clang, but binutils ld can't
			# process LLVM IR bitcode. Using -fno-lto ensures native object files.
			CFLAGS_i686_unknown_linux_gnu = "-fno-lto";
			CXXFLAGS_i686_unknown_linux_gnu = "-fno-lto";
			};
			</syntaxhighlight>
	[[Category:Development]]		[[Category:Development]]

Sewer56: /* Rust */

2025-12-13T09:10:44Z

Rust

← Older revision		Revision as of 09:10, 13 December 2025
Line 24:		Line 24:
	clang_multi		clang_multi
	];		];
	</syntaxhighlight>An example that will let you build with <code>cargo test --target i686-unknown-linux-gnu</code>.		</syntaxhighlight>An example that will let you build with <code>cargo test --target i686-unknown-linux-gnu</code> from an x86_64 machine.

	You will want something similar to the following in your <code>flake.nix</code>, <code>devenv.sh</code> , or whatever you're using as your entry point.		You will want something similar to the following in your <code>flake.nix</code>, <code>devenv.sh</code> , or whatever you're using as your entry point.
	[[Category:Development]]		[[Category:Development]]

Sewer56: /* Building software with both 32- and 64-bit executables */

2025-12-13T09:10:11Z

Building software with both 32- and 64-bit executables

@@ Line 9: / Line 9: @@
 Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
 This is equivalent to using <code>gcc-multilib</code> in debian derivatives.
 [[Category:Development]]

Klinger at 20:42, 24 April 2024

2024-04-24T20:42:11Z

← Older revision		Revision as of 20:42, 24 April 2024
Line 9:		Line 9:
	Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.		Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
	This is equivalent to using <code>gcc-multilib</code> in debian derivatives.		This is equivalent to using <code>gcc-multilib</code> in debian derivatives.
			[[Category:Development]]

imported>Mic92 at 17:54, 19 March 2018

2018-03-19T17:54:18Z

← Older revision		Revision as of 17:54, 19 March 2018
Line 4:		Line 4:
	'''Answer (clever)''': you want to use <code>pkgsi686Linux</code> instead of pkgs, so things like <code>pkgsi686Linux.stdenv.mkDerivation </code> or <code>pkgsi686Linux.callPackage</code> then nix will give you 32bit everything<ref>[https://logs.nix.samueldr.com/nixos/2018-03-19#1521474071-1521474422; clever, #nixos 2018-03-19]</ref>		'''Answer (clever)''': you want to use <code>pkgsi686Linux</code> instead of pkgs, so things like <code>pkgsi686Linux.stdenv.mkDerivation </code> or <code>pkgsi686Linux.callPackage</code> then nix will give you 32bit everything<ref>[https://logs.nix.samueldr.com/nixos/2018-03-19#1521474071-1521474422; clever, #nixos 2018-03-19]</ref>

	== Building ~~multilib~~ software ==		== Building software with both 32- and 64-bit executables ==

	If a package wants to compile both 32/64-bit ~~executable~~, you need a compiler with multilib support.		If a package wants to compile both 32/64-bit executables, you need a compiler with multilib support.
	Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.		Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
	This is equivalent to using <code>gcc-multilib</code> in debian derivatives.		This is equivalent to using <code>gcc-multilib</code> in debian derivatives.

imported>Mic92 at 17:52, 19 March 2018

2018-03-19T17:52:33Z

← Older revision		Revision as of 17:52, 19 March 2018
Line 7:		Line 7:

	If a package wants to compile both 32/64-bit executable, you need a compiler with multilib support.		If a package wants to compile both 32/64-bit executable, you need a compiler with multilib support.
	~~In nixpkgs~~ provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.		Nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
	This is equivalent to using <code>gcc-multilib</code> in debian derivatives.		This is equivalent to using <code>gcc-multilib</code> in debian derivatives.

imported>Mic92 at 17:51, 19 March 2018

2018-03-19T17:51:24Z

← Older revision		Revision as of 17:51, 19 March 2018
Line 6:		Line 6:
	== Building multilib software ==		== Building multilib software ==

	If a ~~packages~~ wants to compile both 32/64-bit executable, you need a compiler with multilib support.		If a package wants to compile both 32/64-bit executable, you need a compiler with multilib support.
	In nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.		In nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
	This is equivalent to using <code>gcc-multilib</code> in debian derivatives.		This is equivalent to using <code>gcc-multilib</code> in debian derivatives.

imported>Mic92 at 17:50, 19 March 2018

2018-03-19T17:50:59Z

← Older revision		Revision as of 17:50, 19 March 2018
Line 7:		Line 7:

	If a packages wants to compile both 32/64-bit executable, you need a compiler with multilib support.		If a packages wants to compile both 32/64-bit executable, you need a compiler with multilib support.
	In nixpkgs provides `multiStdenv.mkDerivation` that should be used instead `stdenv.mkDerivation`.		In nixpkgs provides <code>multiStdenv.mkDerivation</code> that should be used instead <code>stdenv.mkDerivation</code>.
	This is equivalent to using <code>gcc-multilib</code> in debian derivatives.		This is equivalent to using <code>gcc-multilib</code> in debian derivatives.

imported>Mic92: multilib remark

2018-03-19T17:50:14Z

multilib remark

← Older revision		Revision as of 17:50, 19 March 2018
Line 3:		Line 3:
	'''Question''': I'm invoking gcc with -m32 and it fails to find <code>`gnu/stubs-32.h`</code><br/>		'''Question''': I'm invoking gcc with -m32 and it fails to find <code>`gnu/stubs-32.h`</code><br/>
	'''Answer (clever)''': you want to use <code>pkgsi686Linux</code> instead of pkgs, so things like <code>pkgsi686Linux.stdenv.mkDerivation </code> or <code>pkgsi686Linux.callPackage</code> then nix will give you 32bit everything<ref>[https://logs.nix.samueldr.com/nixos/2018-03-19#1521474071-1521474422; clever, #nixos 2018-03-19]</ref>		'''Answer (clever)''': you want to use <code>pkgsi686Linux</code> instead of pkgs, so things like <code>pkgsi686Linux.stdenv.mkDerivation </code> or <code>pkgsi686Linux.callPackage</code> then nix will give you 32bit everything<ref>[https://logs.nix.samueldr.com/nixos/2018-03-19#1521474071-1521474422; clever, #nixos 2018-03-19]</ref>

			== Building multilib software ==

			If a packages wants to compile both 32/64-bit executable, you need a compiler with multilib support.
			In nixpkgs provides `multiStdenv.mkDerivation` that should be used instead `stdenv.mkDerivation`.
			This is equivalent to using <code>gcc-multilib</code> in debian derivatives.

imported>Makefu: Makefu moved page Cross Compiling to Packaging/32bit Applications: not really cross-compiling

2018-03-19T16:27:02Z

Makefu moved page Cross Compiling to Packaging/32bit Applications: not really cross-compiling

← Older revision		Revision as of 16:27, 19 March 2018
(No difference)