From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ckJNg4ch0z2yXl for ; Sat, 11 Oct 2025 09:34:43 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ckJNc2Gw0z2xJy for ; Sat, 11 Oct 2025 09:34:40 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ckJNV49SMz7b; Sat, 11 Oct 2025 09:34:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1760175274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Wk0tOu+yQcCSblqSj4UIP2flmHd6CvcOgYcG/h1zpMg=; b=EzsizL8NHJL86/kZF1a7EtTd1YMEFC83Q6oVn0EqyYksxZG7A71mvhXobBdBGjM/6gLQZm TRUDt4mFEu8C7wzvY+kFPAg4fpn5UPKbbbafQ8nkGV94dirj2iV2/Hh9l+KuStOxbWPkrT irGRwOJRf78le3xdeLbjAmW5YitrUnU5oC97COWBGUwwvYQ5D4PGYnvdLb+KzYESoCvc7W S6Ry6h5Mz1w91ncAmmUL8gwC97UHdfvG6puCqG21hjLsc8nZyFid7UAsKrLFito92t5on2 Fl8mEvI3eBsdNQz/eHre2jPKuNakxHbpNbuJSmiYvCD/U02/mAL4JhNqUErzjA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1760175274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Wk0tOu+yQcCSblqSj4UIP2flmHd6CvcOgYcG/h1zpMg=; b=7WyMzGL4GdeARlgbaHGzQSIUHQ3Tcev6sXqDF7uvg/16Tsia8o+JRc5IeM3LRZlnWOZkmJ SNzKsWoAXog3+FAg== Message-ID: <2e721ea4-a909-4647-93d9-d469794b4734@ipfire.org> Date: Sat, 11 Oct 2025 11:34:31 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: mympd build failure with coreutils-9.8 To: Michael Tremer Cc: "IPFire: Development-List" References: <5988C59A-4BA4-449E-8315-08AA3854659F@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: <5988C59A-4BA4-449E-8315-08AA3854659F@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Michael, On 07/10/2025 17:48, Michael Tremer wrote: > Hello Adolf, > > Interesting question. I would assume that coreutils has a very extensive test suite that will catch any unintended changes in behaviour of any of the tools. I would also rule out that this is an intentional change. That might break a lot of stuff elsewhere. > > I don’t quite understand why myMPD needs this trailing newline, but I would suggest to report upstream and see what they say about it. Thanks for the suggestion. I did that and the developer there said he didn't understand why changes in coreutils would have caused the command used to respond differently. However he also said that he thought the command could be constructed in a better way, which he did and I tested the patch and it worked. So a patch set for coreutils and mympd will be coming along. Regards, Adolf. > > Best, > -Michael > >> On 6 Oct 2025, at 13:19, Adolf Belka wrote: >> >> Hi All, >> >> For information. mympd fails to build when the latest version of coreutils (9.8) is used. >> >> Looking at the failure message that occurs >> >> ----------------------------------------- >> >> Oct 5 20:34:30: Building mympd make: Entering directory '/home/ahb/sandbox/ipfire-2-builder2/lfs' >> make: Nothing to be done for 'download'. >> make: Leaving directory '/home/ahb/sandbox/ipfire-2-builder2/lfs' >> make: Entering directory '/usr/src/lfs' >> myMPD-22.0.4.tar.gz checksum OK >> ====================================== Installing myMPD-22.0.4 ... >> Install started; saving file list to /usr/src/lsalr ... >> # Do not try to re-define _FORTIFY_SOURCE >> cd /usr/src/myMPD-22.0.4 && sed -e "/D_FORTIFY_SOURCE/d" -i CMakeLists.txt >> cd /usr/src/myMPD-22.0.4 && mkdir -p build >> cd /usr/src/myMPD-22.0.4/build && cmake -Wno-dev \ >> -DCMAKE_INSTALL_PREFIX=/usr \ >> -DCMAKE_BUILD_TYPE=Release .. >> -- The C compiler identification is GNU 15.2.0 >> -- Detecting C compiler ABI info >> -- Detecting C compiler ABI info - done >> -- Check for working C compiler: /tools_x86_64/ccache/bin/cc - skipped >> -- Detecting C compile features >> -- Detecting C compile features - done >> Cmake version: 4.1.1 >> Cmake src dir: /usr/src/myMPD-22.0.4 >> Cmake build dir: /usr/src/myMPD-22.0.4/build >> Cmake build type: Release >> Cmake generator: Unix Makefiles >> Compiler: GNU 15.2.0 >> CMAKE_C_FLAGS: -O2 -g0 -pipe -Wall -fexceptions -fPIC -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -fstack-clash-protection -m64 -mtune=generic -fcf-protection=full >> CMAKE_EXE_LINKER_FLAGS: >> Arch: >> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD >> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success >> -- Found Threads: TRUE >> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") >> -- Found PCRE2: /usr/lib/libpcre2-8.so >> -- Found OpenSSL: /usr/lib64/libcrypto.so (found version "3.5.1") >> Searching for libid3tag >> -- Found LIBID3TAG: /usr/lib/libid3tag.so >> Searching for flac >> -- Found FLAC: /usr/lib/libFLAC.so >> Searching for lua >> -- Found Lua: /usr/lib/liblua.so;/usr/lib/libm.so (found version "5.4.7") >> Searching for libmygpio >> -- Could NOT find LIBMYGPIO (missing: LIBMYGPIO_LIBRARY LIBMYGPIO_INCLUDE_DIR) >> Compiling static version of libmygpio >> Executables in: /usr/bin >> Workdir: /var/lib/mympd >> Cachedir: /var/cache/mympd >> Embedding assets in binary >> Creating assets in /usr/src/myMPD-22.0.4/build >> Validating translation phrases >> Creating i18n json >> Minifying /usr/src/myMPD-22.0.4/build/htdocs/js/i18n.js >> Creating version file >> Minifying javascript >> Creating mympd.js >> Minifying htdocs/sw.js >> Minifying /usr/src/myMPD-22.0.4/build/htdocs/js/mympd.js >> Combining and compressing javascript >> ERROR: dist/bootstrap-native/bootstrap-native.min.js don't end with newline character >> CMake Error at CMakeLists.txt:198 (message): >> Creating assets failed >> >> >> -- Configuring incomplete, errors occurred! >> make: *** [mympd:87: /usr/src/log/myMPD-22.0.4] Error 1 >> >> ----------------------------------------- >> >> I found that the "Combining and compressing javascript comment is in the build.sh file in the top level of the mympd tarball. >> >> In build.sh there is a section >> >> ----------------------------------------- >> echo "Combining and compressing javascript" >> echo "//${COPYRIGHT}" > "$MYMPD_BUILDDIR/htdocs/js/copyright.min.js" >> if [ "$MYMPD_MINIFY_JS" = "0" ] >> then >> JSFILES="dist/bootstrap-native/bootstrap-native.js dist/long-press-event/long-press-event.js" >> else >> JSFILES="dist/bootstrap-native/bootstrap-native.min.js dist/long-press-event/long-press-event.min.js" >> fi >> JSFILES="$JSFILES $MYMPD_BUILDDIR/htdocs/js/*.min.js" >> for F in $JSFILES >> do >> if tail -1 "$F" | perl -npe 'exit 1 if m/\n/; exit 0' >> then >> echo_error "$F don't end with newline character" >> exit 1 >> fi >> done >> ----------------------------------------- >> >> and this has the error message that is shown. The file mentioned just has a single line of the js code. >> >> This section uses the tail command and that command is one that has had 25 commits applied to it in coreutils-9.8 >> >> I am not sure if this error is due to a problem in mympd or if there are errors in mympd which are now being flagged up by the updated coreutils. >> >> I have not been able to find any mention of this issue currently. >> >> I also tested it with the latest version of mympd (22.1.0) but that also ended up with the same error message. >> >> Regards, >> >> Adolf. >> >> >