Build error on Debian 12 i386

[n9]

I am trying to build dosemu2 on Debian 12 i386 (following the instructions). The build fails:

$ make deb
debuild -i -us -uc -b
 dpkg-buildpackage -us -uc -ui -i -b
dpkg-buildpackage: info: source package fdpp
dpkg-buildpackage: info: source version 1.9-1
dpkg-buildpackage: info: source distribution noble
dpkg-buildpackage: info: source changed by Stas Sergeev <stsp@users.sourceforge.net>
 dpkg-source -i --before-build .
dpkg-buildpackage: info: host architecture i386
dpkg-checkbuilddeps: error: Unmet build dependencies: clang nasm-segelf binutils-x86-64-linux-gnu libelf-dev thunk-gen pkg-config
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -b failed
make: *** [makefile:15: deb] Error 29

[stsp]

Have you performed the previous
step, that says
mk-build-deps --install --root-cmd sudo --remove?

Also the doc you refer to,
is for debian 11, not 12.
Would someone like to
write the debian-12 instructions?
@jschwartzenberg or @andrewbird
or maybe even @skitt can do that? :)

[n9]

@stsp Yes, but I have not noticed the error:

$ mk-build-deps --install --root-cmd sudo --remove
dpkg-buildpackage: info: source package fdpp-build-deps
dpkg-buildpackage: info: source version 1.9-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Equivs Dummy Package Generator <builder@asusm9v>
dpkg-buildpackage: info: host architecture i386
 dpkg-source --before-build .
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/fdpp-build-deps/
   dh_install
   dh_installdocs
   dh_installchangelogs
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_installdeb
   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'fdpp-build-deps' in '../fdpp-build-deps_1.9-1_all.deb'.
 dpkg-genbuildinfo --build=binary -O../fdpp-build-deps_1.9-1_i386.buildinfo
 dpkg-genchanges --build=binary -O../fdpp-build-deps_1.9-1_i386.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)

The package has been created.
Attention, the package has been created in the current directory,
not in ".." as indicated by the message above!
[sudo] password for builder:
Selecting previously unselected package fdpp-build-deps.
(Reading database ... 213033 files and directories currently installed.)
Preparing to unpack fdpp-build-deps_1.9-1_all.deb ...
Unpacking fdpp-build-deps (1.9-1) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) fdpp-build-deps:i386 < 1.9-1 @iU K Nb Ib >
Broken fdpp-build-deps:i386 Depends on nasm-segelf:i386 < none @un H >
  Removing fdpp-build-deps:i386 because I can't find nasm-segelf:i386
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  fdpp-build-deps
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 9,216 B disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 213037 files and directories currently installed.)
Removing fdpp-build-deps (1.9-1) ...
mk-build-deps: Unable to install fdpp-build-deps at /usr/bin/mk-build-deps line 459.
mk-build-deps: Unable to install all build-dep packages

[stsp]

I think @skitt haven't added
nasm-segelf to debian-12...
@skitt could you please update
us about the status of that
process?

In a mean time you can try
to clone nasm-segelf repo
and do make deb also there.

[stsp]

This is a make bug actually.
Instead of saying this, it had
to tell you that makefile is missing.
You may want to report this
to GNU make upstream.

You need to create makefile
first, for which run ./configure.

[n9]

Ok, thank you I have realized that in the meantime.

I have successfully build and installed nasm-segelf.

But problems with fdpp deps still persist:

$ mk-build-deps --install --root-cmd sudo --remove
dpkg-buildpackage: info: source package fdpp-build-deps
dpkg-buildpackage: info: source version 1.9-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Equivs Dummy Package Generator <builder@asusm9v>
dpkg-buildpackage: info: host architecture i386
 dpkg-source --before-build .
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/fdpp-build-deps/
   dh_install
   dh_installdocs
   dh_installchangelogs
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_installdeb
   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'fdpp-build-deps' in '../fdpp-build-deps_1.9-1_all.deb'.
 dpkg-genbuildinfo --build=binary -O../fdpp-build-deps_1.9-1_i386.buildinfo
 dpkg-genchanges --build=binary -O../fdpp-build-deps_1.9-1_i386.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)

The package has been created.
Attention, the package has been created in the current directory,
not in ".." as indicated by the message above!
Selecting previously unselected package fdpp-build-deps.
(Reading database ... 213038 files and directories currently installed.)
Preparing to unpack fdpp-build-deps_1.9-1_all.deb ...
Unpacking fdpp-build-deps (1.9-1) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) fdpp-build-deps:i386 < 1.9-1 @iU K Nb Ib >
Broken fdpp-build-deps:i386 Depends on thunk-gen:i386 < none @un H >
  Removing fdpp-build-deps:i386 because I can't find thunk-gen:i386
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  fdpp-build-deps
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 9,216 B disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 213042 files and directories currently installed.)
Removing fdpp-build-deps (1.9-1) ...
mk-build-deps: Unable to install fdpp-build-deps at /usr/bin/mk-build-deps line 459.
mk-build-deps: Unable to install all build-dep packages

[n9]

I will try to build and install thunk_gen.

[n9]

But the instruction says: It is likely not interesting for you unless you want to compile some 16bit or 32bit DOS code for 64-bits execution.

I am trying to install dosemu2 on i386 (not 64 bit). Do I need thunk_gen and fdpp?

[stsp]

Yes, you still need this as in
this case it helps building
16bit freedos code for 32bit
platform (which is not mentioned
there).

However, it was supposed to
be already in debian:
https://packages.debian.org/search?keywords=thunk-gen
So I am not entirely sure what
is the problem here exactly.

[jschwartzenberg]

So I am not entirely sure what
is the problem here exactly.

We're using Debian 12/Bookworm. It's the current stable version and that package is listed only for testing. This means it will only be in Debian 13/Trixie.

@n9 indeed you need to compile a few more packages, but everything works on Debian 12 i386. It was also on the system on which @stsp was debugging the issues I reported in the tickets that were recently closed. Some assumptions from the instructions and precompiled packages are just not meant for i386.

If the Ubuntu PPA could be enhanced with i386 packages, we could probably use those. The current Raspberry Pi OS for ARM64 is also based on Debian Bookworm. I could install the packages for Ubuntu 22.04 on it without problems and DOSEMU "just worked" after that. So if Launchpad could be tweaked to build Ubuntu 22.04 packages for i386, we could use those instead. I don't know if i386 is still supported. (Tried 24.04 packages too, but those depend on libraries which are newer than those on Bookworm.)

[stsp]

Thanks for info.
LP is fine with i386, but
Ubuntu itself have dropped
i386 since Focal, so you can
build for i386 only if for
something older than Focal.
And we do not support
anything before Focal, so
lets say LP is not an option
here.

So updating the doc is an
only option. Please do, if
you have some time for that. :)

[n9]

What about flatpak? Will it be possible to deliver dosemu via flatpak?

[stsp]

make flatpak-build.

[n9]

I mean instead of writing documentation for particular distro and version, what about to use CI to create Flatpak and publish it to Flathub or other repository?

[stsp]

Its already there, eg:
https://github.com/dosemu2/dosemu2/actions/runs/14684139485/job/41210565880

[stsp]

But of course this doesn't
replace the distro-specific
docs.