https://sourceware.org/bugzilla/show_bug.cgi?id=30779
--- Comment #2 from Vladimir Mezentsev <vladimir.mezentsev at oracle dot com> --- I don't use musl. But I fixed couple bugs in gprofng to build on x86_64-pc-linux-musl. I did on my machine: % wget https://distfiles.adelielinux.org/adelie/1.0/iso/rc2/adelie-rootfs-mini-x86_64-1.0-rc2.txz % sudo tar xf adelie-rootfs-mini-x86_64-1.0-rc2.txz % sudo systemd-nspawn --directory=. -M mez_musl Spawning container mez_musl on /data2/vmezents/musl. Press ^] three times within 1s to kill container. -sh: 0: can't access tty; job control turned off /sbin/apk add bash && bash /sbin/apk add build-tools m4 bison flex gmp-dev texinfo cd /home && mkdir bld && cd bld ../binutils-gdb.git/configure --prefix=`pwd`/INSTALL --enable-multilib --disable-gdb --disable-gdbsupport --disable-gdbserver I fixed the compiler errors (open64, fgetpo64 and fsetpos64 are redefined) in gprofng. But I don't see errors about off64_t or ino64_t. I use this system: % uname -a Linux mez_musl 5.4.17-2136.318.7.1.el8uek.x86_64 #2 SMP Thu Apr 13 17:33:39 PDT 2023 x86_64 GNU/Linux My questions are: How can I simply use/download musl-1.2.4 ? Is the bug on Arm or on Intel ? -- You are receiving this mail because: You are on the CC list for the bug.
