Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > muc.lists.freebsd.emulation > #12755 > unrolled thread

[Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE

Started bybugzilla-noreply@freebsd.org
First post2025-12-04 12:53 +0000
Last post2026-07-01 01:02 +0000
Articles 7 on this page of 47 — 1 participant

Back to article view | Back to muc.lists.freebsd.emulation


Contents

  [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2025-12-04 12:53 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2025-12-04 12:56 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-14 23:22 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-14 23:27 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-15 21:35 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-15 21:35 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-15 21:37 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-15 23:52 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-16 19:33 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-25 00:17 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-25 00:27 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-05-28 06:41 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 19:57 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 20:00 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 20:03 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 20:06 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 20:12 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 23:04 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 23:09 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-20 23:25 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-21 15:14 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 01:56 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 02:02 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 03:43 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 06:07 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 14:35 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 19:15 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 20:56 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 22:55 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 23:19 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 23:48 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-22 23:49 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 00:17 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 00:19 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 00:49 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 01:21 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 01:54 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 02:21 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 05:07 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 16:00 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 16:37 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 17:57 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 18:42 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-23 22:23 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-30 23:35 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-06-30 23:32 +0000
    [Bug 291390] emulators/qemu-user-static: poudriere build fails on both 14-STABLE and 15-STABLE bugzilla-noreply@freebsd.org - 2026-07-01 01:02 +0000

Page 3 of 3 — ← Prev page 1 2 [3]


#13024

Frombugzilla-noreply@freebsd.org
Date2026-06-23 16:37 +0000
Message-ID<bug-291390-4077-swuP796pwC@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #40 from Sulev-Madis Silber <bugs-freebsd-org916@ketas.si.pri.ee> ---
i don't have .a

i noticed it before too even

and that's because devel/pcre2 has

Options        :
...
        STATIC         : off

it's defaults were changed, and, again, nothing has noticed me for options
review

i have been told to manually override options and not used menus but this would
be even more work

unsure what others do, do they have options disabled, do they only use
poudriere, do they periodically wipe options, just to check if anything new
appeared?

maybe options merge prompt is needed somewhere. i didn't check if updating
entry exists but nobody reads it anyway

unsure what could be done here. options are often used, you can select between
multiple ssl libs, nginx has modules, and perhaps to avoid half desktop to be
installed in headless machine

while there, why uboot build has cups in it's dep chain?

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13026

Frombugzilla-noreply@freebsd.org
Date2026-06-23 17:57 +0000
Message-ID<bug-291390-4077-2bq2OIXNcH@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #41 from Alexey Shuvaev <bugsbeastie@gmail.com> ---
(In reply to Sulev-Madis Silber from comment #40)
First, have you managed to recompile pcre2 with STATIC OPTION ON and then
(re-)compile qemu-user-static? :)

As for the u-boot-* ports, which one do you have?
An example of the poudriere build log for u-boot-rock-pi-4-2025.10 (no cups
installed):

=======================<phase: build-depends  >============================
===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0
===>   u-boot-rock-pi-4-2025.10 depends on executable: gsed - not found
===>   Installing existing package /packages/All/gsed-4.10.pkg
[16amd64-default-job-01] Installing gsed-4.10...
[16amd64-default-job-01] `-- Installing gettext-runtime-1.0_1...
[16amd64-default-job-01] |   `-- Installing indexinfo-0.3.1_1...
[16amd64-default-job-01] |   `-- Extracting indexinfo-0.3.1_1: .... done
[16amd64-default-job-01] `-- Extracting gettext-runtime-1.0_1: .......... done
[16amd64-default-job-01] Extracting gsed-4.10: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on executable: gsed - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on executable: swig - not found
===>   Installing existing package /packages/All/swig-4.4.1.pkg
[16amd64-default-job-01] Installing swig-4.4.1...
[16amd64-default-job-01] `-- Installing pcre2-10.47_1...
[16amd64-default-job-01] `-- Extracting pcre2-10.47_1: .......... done
[16amd64-default-job-01] Extracting swig-4.4.1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on executable: swig - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on package: dtc>=1.4.1 - not found
===>   Installing existing package /packages/All/dtc-1.7.1.pkg
[16amd64-default-job-01] Installing dtc-1.7.1...
[16amd64-default-job-01] `-- Installing libyaml-0.2.5...
[16amd64-default-job-01] `-- Extracting libyaml-0.2.5: ......... done
[16amd64-default-job-01] Extracting dtc-1.7.1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on package: dtc>=1.4.1 - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on executable: mkimage - not found
===>   Installing existing package /packages/All/u-boot-tools-2025.10.pkg
[16amd64-default-job-01] Installing u-boot-tools-2025.10...
[16amd64-default-job-01] `-- Installing gnutls-3.8.13...
[16amd64-default-job-01] |   `-- Installing brotli-1.2.0,1...
[16amd64-default-job-01] |   `-- Extracting brotli-1.2.0,1: .......... done
[16amd64-default-job-01] |   `-- Installing gmp-6.3.0...
[16amd64-default-job-01] |   `-- Extracting gmp-6.3.0: .......... done
[16amd64-default-job-01] |   `-- Installing libidn2-2.3.8...
[16amd64-default-job-01] |   | `-- Installing libunistring-1.4.2...
[16amd64-default-job-01] |   | `-- Extracting libunistring-1.4.2: ..........
done
[16amd64-default-job-01] |   `-- Extracting libidn2-2.3.8: .......... done
[16amd64-default-job-01] |   `-- Installing libtasn1-4.21.0...
[16amd64-default-job-01] |   `-- Extracting libtasn1-4.21.0: .......... done
[16amd64-default-job-01] |   `-- Installing nettle-3.10.2...
[16amd64-default-job-01] |   `-- Extracting nettle-3.10.2: .......... done
[16amd64-default-job-01] |   `-- Installing p11-kit-0.26.2...
[16amd64-default-job-01] |   | `-- Installing libffi-3.5.2...
[16amd64-default-job-01] |   | `-- Extracting libffi-3.5.2: .......... done
[16amd64-default-job-01] |   `-- Extracting p11-kit-0.26.2: .......... done
[16amd64-default-job-01] |   `-- Installing zstd-1.5.7_2...
[16amd64-default-job-01] |   | `-- Installing liblz4-1.10.0_2,1...
[16amd64-default-job-01] |   | `-- Extracting liblz4-1.10.0_2,1: ..........
done
[16amd64-default-job-01] |   `-- Extracting zstd-1.5.7_2: .......... done
[16amd64-default-job-01] `-- Extracting gnutls-3.8.13: .......... done
[16amd64-default-job-01] Extracting u-boot-tools-2025.10: ....... done
===>   u-boot-rock-pi-4-2025.10 depends on executable: mkimage - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on package: py311-setuptools-pkg>=0 -
not found
===>   Installing existing package /packages/All/py311-setuptools-pkg-0.9_1.pkg
[16amd64-default-job-01] Installing py311-setuptools-pkg-0.9_1...
[16amd64-default-job-01] `-- Installing py311-setuptools-63.1.0_3...
[16amd64-default-job-01] |   `-- Installing python311-3.11.15_2...
[16amd64-default-job-01] |   | `-- Installing mpdecimal-4.0.1...
[16amd64-default-job-01] |   | `-- Extracting mpdecimal-4.0.1: .......... done
[16amd64-default-job-01] |   | `-- Installing readline-8.3.3...
[16amd64-default-job-01] |   | `-- Extracting readline-8.3.3: .......... done
[16amd64-default-job-01] |   `-- Extracting python311-3.11.15_2: ..........
done
[16amd64-default-job-01] `-- Extracting py311-setuptools-63.1.0_3: ..........
done
[16amd64-default-job-01] Extracting py311-setuptools-pkg-0.9_1: .......... done
=====
Message from python311-3.11.15_2:

--
Note that some standard Python modules are provided as separate ports
as they require additional dependencies. They are available as:

py311-gdbm       databases/py-gdbm@py311
py311-sqlite3    databases/py-sqlite3@py311
py311-tkinter    x11-toolkits/py-tkinter@py311
===>   u-boot-rock-pi-4-2025.10 depends on package: py311-setuptools-pkg>=0 -
found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on executable: aarch64-none-elf-gcc -
not found
===>   Installing existing package
/packages/All/aarch64-none-elf-gcc-11.3.0_3.pkg
[16amd64-default-job-01] Installing aarch64-none-elf-gcc-11.3.0_3...
[16amd64-default-job-01] `-- Installing aarch64-none-elf-binutils-2.44,1...
[16amd64-default-job-01] `-- Extracting aarch64-none-elf-binutils-2.44,1:
.......... done
[16amd64-default-job-01] `-- Installing mpc-1.4.1...
[16amd64-default-job-01] |   `-- Installing mpfr-4.2.2,1...
[16amd64-default-job-01] |   `-- Extracting mpfr-4.2.2,1: .......... done
[16amd64-default-job-01] `-- Extracting mpc-1.4.1: .......... done
[16amd64-default-job-01] Extracting aarch64-none-elf-gcc-11.3.0_3: ..........
done
===>   u-boot-rock-pi-4-2025.10 depends on executable: aarch64-none-elf-gcc -
found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on package: gnutls>=0 - found
===>   u-boot-rock-pi-4-2025.10 depends on file:
/usr/local/share/atf-rk3399/bl31.elf - not found
===>   Installing existing package /packages/All/atf-rk3399-v2.10.6.pkg
[16amd64-default-job-01] Installing atf-rk3399-v2.10.6...
[16amd64-default-job-01] Extracting atf-rk3399-v2.10.6: .... done
===>   u-boot-rock-pi-4-2025.10 depends on file:
/usr/local/share/atf-rk3399/bl31.elf - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on package: py311-pyelftools>0 - not
found
===>   Installing existing package /packages/All/py311-pyelftools-0.32.pkg
[16amd64-default-job-01] Installing py311-pyelftools-0.32...
[16amd64-default-job-01] Extracting py311-pyelftools-0.32: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on package: py311-pyelftools>0 - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on executable: bison - not found
===>   Installing existing package /packages/All/bison-3.8.2_2,1.pkg
[16amd64-default-job-01] Installing bison-3.8.2_2,1...
[16amd64-default-job-01] `-- Installing libtextstyle-1.0...
[16amd64-default-job-01] `-- Extracting libtextstyle-1.0: .......... done
[16amd64-default-job-01] `-- Installing m4-1.4.21,1...
[16amd64-default-job-01] `-- Extracting m4-1.4.21,1: .......... done
[16amd64-default-job-01] Extracting bison-3.8.2_2,1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on executable: bison - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on package: gmake>=4.4.1 - not found
===>   Installing existing package /packages/All/gmake-4.4.1.pkg
[16amd64-default-job-01] Installing gmake-4.4.1...
[16amd64-default-job-01] Extracting gmake-4.4.1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on package: gmake>=4.4.1 - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===>   u-boot-rock-pi-4-2025.10 depends on file: /usr/local/bin/python3.11 -
found
===>   u-boot-rock-pi-4-2025.10 depends on package: pkgconf>=1.3.0_1 - not
found
===>   Installing existing package /packages/All/pkgconf-2.4.3_1,1.pkg
[16amd64-default-job-01] Installing pkgconf-2.4.3_1,1...
[16amd64-default-job-01] Extracting pkgconf-2.4.3_1,1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on package: pkgconf>=1.3.0_1 - found
===>   Returning to build of u-boot-rock-pi-4-2025.10
===========================================================================
=======================<phase: lib-depends    >============================
===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0
===>   u-boot-rock-pi-4-2025.10 depends on shared library: libuuid.so - not
found
===>   Installing existing package /packages/All/libuuid-2.42.1.pkg
[16amd64-default-job-01] Installing libuuid-2.42.1...
[16amd64-default-job-01] Extracting libuuid-2.42.1: .......... done
===>   u-boot-rock-pi-4-2025.10 depends on shared library: libuuid.so - found
(/usr/local/lib/libuuid.so)
===>   Returning to build of u-boot-rock-pi-4-2025.10
===========================================================================
=======================<phase: configure      >============================
===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13027

Frombugzilla-noreply@freebsd.org
Date2026-06-23 18:42 +0000
Message-ID<bug-291390-4077-YHVHnn0nP1@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #42 from Sulev-Madis Silber <bugs-freebsd-org916@ketas.si.pri.ee> ---
no, but i probably will able to build now if i try


as for cups, i have to check but iirc it still was some uboot that on poudriere
asked options for cups

i have new uboot/atf subports (also in bugzilla) and i think it was that

anyway it was surprising dep chain which probably can't be changed

with so little effort, behemoths such as rust also come in

btw, can qemu user now build rust? would be likely running for the better part
of a week but at least will build


as for my and others, i bet half of people had pcre2 with old opts unless they
had some other issues

also it's totally cursed how things never told what the actual problem was,
right on the console

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13028

Frombugzilla-noreply@freebsd.org
Date2026-06-23 22:23 +0000
Message-ID<bug-291390-4077-C67ijr3Fnr@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #43 from Sulev-Madis Silber <bugs-freebsd-org916@ketas.si.pri.ee> ---
so it's building now

but i'm puzzled how i was able to build that qemu once back in 13? was it
different pcre2? i haven't changed options either. qemu is one of those that
was still from 13 since it didn't build anymore after i went to 14. along with
few llvm's (long build times)

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13030

Frombugzilla-noreply@freebsd.org
Date2026-06-30 23:35 +0000
Message-ID<bug-291390-4077-MDdMxLvmcS@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #45 from Alexey Shuvaev <bugsbeastie@gmail.com> ---
Now, that sizeof(size_t) problem is pinned down to devel/pcre2 being compiled
without static libraries (old default OPTIONS), can anybody here with the ports
commit bit commit the update?

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13031

Frombugzilla-noreply@freebsd.org
Date2026-06-30 23:32 +0000
Message-ID<bug-291390-4077-naVxSA3R6t@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #44 from Alexey Shuvaev <bugsbeastie@gmail.com> ---
(In reply to Sulev-Madis Silber from comment #42)
> btw, can qemu user now build rust?
> would be likely running for the better part of a week but at least will build

Hi!
Well, see:
On 16amd64 jail building perl5-5.42.2 native with 4 cores of core i5-3550 @
3.30 GHz takes 00:05:40 (5-6 minutes).
The 16arm64 jail cross-builds perl5-5.42.2 with qemu-user-static on the same
hardware in 01:31:19 (90 minutes). This is roughly 20 times slower.
Again, 16amd64 jail (same hardware) builds rust-1.96.0_1 in 06:20:58 (380
minutes). Projecting 20 times slower speed gives 7600 minutes -> 126 hours -> 5
days.
Yes, one week.

But, as I mentioned in the comment #16 and comment #17, I have not succeeded
with even lang/python311 port. Probably you would not get to rust either!

emulators/qemu-user-static-devel is more promising, see bug #286875, but it is
still not in the good shape!

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [next] | [standalone]


#13032

Frombugzilla-noreply@freebsd.org
Date2026-07-01 01:02 +0000
Message-ID<bug-291390-4077-Nrab0ro7FR@https.bugs.freebsd.org/bugzilla/>
In reply to#12755
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291390

--- Comment #46 from Sulev-Madis Silber <bugs-freebsd-org916@ketas.si.pri.ee> ---
there was once a pissed developer in mailing lists who didn't get why freebsd
isn't like linux and won't allow building base and ports under a normal user
privileges, with newer or older host as builder

i only had to comment, which didn't satisfy him, that probably every freebsd
hardware developer has full lab with all architectures and versions running on
real hardware and won't be scared to run things under root on a very dangerous
current. and for this reason things were never changed

maybe he was trolling too since i don't believe actual embedded hardware
manufacturer is single man operation with only one personal laptop. which can
break. nevermind the huge security implications. you really can't break out of
the physical hardware. and you no longer need to book an appointment and bring
punch cards to get some code compiled on country's only good computer located
at prominent university lab

well i don't know. i used to run some things on full emulation in qemu armv7 vm
on a c2d machine. some operations, or should i say portupgrade portsdb
generations still took just seconds even on that e-waste class hardware. but it
took 6 hours!!! in vm. compilation mostly worked, with some questionable
errors. but it still was very very very slow. but funnily why was ssh into it
so responsible. it ran part ufs on zfs file. part nfs. but speed is such that i
don't think i've seen that on any real hardware, and i regularly have ran old
stuff

p.s.; still don't know how i made uboot building depend on cups but i'm still
sure i didn't see things there. but it's not unusual to see default options
bringing half of xorg into headless server and so on. nevermind the build tools
bring every know scripting language into machine and so on

just recently i opted to run 13.x built armv7 ports on 16.x kernel and world
because it was simpler to work out the kinks there than to get 16.x ports
built. but this is clearly not business production environment, otherwise i
would just run all on own hardware

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [standalone]


Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | muc.lists.freebsd.emulation


csiph-web