From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4Zv7hV3WDsz334Q for ; Fri, 9 May 2025 12:33:30 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4Zv7hQ72yrz2y59 for ; Fri, 9 May 2025 12:33:26 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4Zv7hQ2m7Xz2X6; Fri, 9 May 2025 12:33:26 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1746794006; 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=4ZMUdiiABp2nD6P/4L2+bIKklN2rHaMqrHHFP5N34ns=; b=0irxjTkJ/ERuW23zbhvzDZ4aCLewlPOdaAAUioRpGbU2DRYmbyC8zrcmr7iNZqB+U2odRh 7W/Zko4ZFiIU+0Cg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1746794006; 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=4ZMUdiiABp2nD6P/4L2+bIKklN2rHaMqrHHFP5N34ns=; b=rvPN1g9f7jMu1mM0pFucKQHC8pyXdEDNr29CgRcXAYrMe1pz519METB1YmEXBfsCwvZS74 M7mH8oDkOscWH4kXUIUPTAEW4tKN2wgYoU1d+Hp+UXoBryX1GfzZoF5XOP1xne2/AjMH8Y zftRx4Q+NkQHDGAw2iBE1mGtNoJ9njHUEdxDhPR6OYq0pgku2BKoSy2R7SDIzI2uM0PJ4S h9ZmxUkIuNzkMBI1FEYKl2/RXBvrB1CFsjIxgao3wvdoHxxHRMbZcgYY3C6hs/Zy6rsAGf ATVtkW+NDXX/bQbZCY6T2Z//cmEkeviHQdi5dqYcphFDZLvRHSAOoEyWSxkWkg== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Problem building cdrkit with latest cmake From: Michael Tremer In-Reply-To: <425a82d7-dc7b-4aa3-953e-f16d7c3e2835@ipfire.org> Date: Fri, 9 May 2025 13:33:25 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <8f4f56f8-2dd5-4d4d-a1d0-aa2c88455c54@ipfire.org> <425a82d7-dc7b-4aa3-953e-f16d7c3e2835@ipfire.org> To: Adolf Belka Hello, > On 9 May 2025, at 11:02, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 08/05/2025 21:00, Adolf Belka wrote: >> Hi Michael, >> On 08/05/2025 15:19, Michael Tremer wrote: >>> Hello Adolf, >>>=20 >>> Yet another success store of an alternative to configure/make/make = install. >>>=20 >>> I remember this from IPFire 3 where we have made the transition to = libburn. It needs three packages: >>>=20 >>> = https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dblob;f=3Dlibburn/libburn.nm= ;hb=3Df1a186fd032e8e5718e41120a27103c83ed69a3e >>> = https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dblob;f=3Dlibisofs/libisofs.= nm;hb=3Df1a186fd032e8e5718e41120a27103c83ed69a3e >>> = https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dblob;f=3Dlibisoburn/libisob= urn.nm;hb=3Df1a186fd032e8e5718e41120a27103c83ed69a3e >>>=20 >>> We are using the whole thing here: >>>=20 >>> = https://git.ipfire.org/?p=3Dpeople/ms/bricklayer.git;a=3Dblob;f=3Dsrc/bric= klayer-master.in;hb=3D3b216919f31dc6ca3b44d9d25536626b60aea9f1#l527 >>>=20 >>> So it seems to generate a bootable ISO and that is all we need. >>>=20 >>> Happy to make the transition in IPFire 2 as well. >> I think for IPFire-2 we can just use the xorriso package that libburn = supplies to the Gnu Project. >> This is a self contained source tarball that includes the bits from = libisofs and libisoburn, sufficient to do the cli commands for xorriso = and xorrisofs. >> https://www.gnu.org/software/xorriso/ >> I think this makes it simpler for IPFire-2 and it supplies what is = needed for creating a bootable ISO. >> My plan would be to follow this path unless you think that installing = the three full packages that you listed is the better thing to do also = for IPFire-2. >=20 > I did a test build of the xorriso package and made a symbolic link of = xorrisofs to mkisofs in the LFS so that no changes should be needed = anywhere else. Anything using mkisofs would then use xorrisofs with the = same arguments as used for mkisofs. >=20 > It successfully produced an iso, which was bootable as I was able to = install IPFire with it onto my vm testbed. That is good news. > Couldn't test out the making of the backupiso as that downloads the = current released iso and my test build is with CU195. >=20 > Are you okay with using the xorriso source tarball or should I do a = build and patch submit with the full libburn, libisofs & libisoburn = packages? We don=E2=80=99t have any other use for the libraries, so I am happy to = take the fast path - provided it is also being updated regularly like = the other packages. > The Gnu xorriso site says >=20 > " Software copies included in GNU xorriso: > GNU xorriso is feature-wise equivalent to the dynamic compilation of = libburnia libraries, libjte, and libburnia program xorriso. It restricts = itself to a technical form where the legal commitments of the libburnia = project and the legal intentions of FSF match completely." >=20 > so it is clearly a limited form but it looks like it should be = sufficient for IPFire-2.x. Perfect! No idea why I made it so complicated in IPFire 3. Maybe because = I don=E2=80=99t like bundled libraries :) -Michael > Regards, >=20 > Adolf. >=20 >> Regards, >> Adolf. >>>=20 >>> -Michael >>>=20 >>>> On 8 May 2025, at 13:53, Adolf Belka = wrote: >>>>=20 >>>> Hi Everyone. >>>>=20 >>>> I found that curl had three updates for a range of bug fixes and so = I went ahead and ran a build of curl-1.13.0. It built without any = problems. >>>>=20 >>>> However cmake, a couple of steps later failed to build because of = some changes in curl to certain names. >>>>=20 >>>> So I installed the latest cmake and then curl and cmake both built = without any issues. >>>>=20 >>>> Then json-c failed due to the min ver of cmake being supported is = now 3.5 and in the near future this will be changed to 3.10. >>>>=20 >>>> I found a patch from json-c that changed the minimum required = version from 2.8 to 3.9...3.12 and json-c then successfully built. >>>>=20 >>>> libjpeg successfully built as it already had an acceptable min = cmake version. >>>>=20 >>>> libssh failed to build so it was updated to 0.11.1 and this built = successfully. >>>>=20 >>>> Then I came to cdrkit!!! >>>>=20 >>>> This failed to build due to too low a min version so I changed the = min version from 2.8 to 3.25 but it the failed to build due to the = cmake_policy(SET CMPOO15 OLD) and OLD is no longer allowed. It has to be = NEW. >>>> So I changed the policy to NEW and then it starting building cdrkit = but then the build failed due to the fact that it could not find = xconfig.h >>>> In the source file there is xconfig.h.in but it is not getting = built into xconfig.h >>>>=20 >>>> I checked for the existing build that works and found that there = were 83 CMAKE Warnings, all related to the fact that Policy CMP0115 is = not set. The cmake_policy value in the existing patch was set at CMP0015 = so I also tried using cmake_policy(SET CMP0115 NEW) but that still = stopped with the missing xconfig.h >>>>=20 >>>> It looks like the NEW cmake_policy no longer allows error to be = ignored and building to continue as has been the case up to date. >>>>=20 >>>> It looks to me like the only way to fix it is to update cdrkit to = properly work with the latest cmake but as the existing version was = released 15 years ago and nothing further has been done with it I think = it will not get fixed. >>>>=20 >>>> There is also cdrtools but there are some questions raised by some = distros about it's licence. However the developer of that package died = and so nothing further has been done with that for the last 7 years. >>>>=20 >>>> I did find that there is a project called libburnia that has a = command line package called xorrisofs which emulates mkisofs. >>>> All the mkisofs options that we use in IPFire are available with = xorrisofs. The project had the last release of xorriso in 2023 but it = looks like the package is released around every two years. The last = commits for the project were done 2 weeks ago and there looks to be a = continuing ongoing level of commit updates being done. >>>>=20 >>>> Would it be worthwhile for me to look at building this package and = make the changes in the cdrom sections to use xorrisofs instead of = mkisofs and see if its emulation of mkisofs produces a working IPFire = iso that can be successfully installed and run? >>>>=20 >>>> If the answer is not a simple one to give then we can discuss this = issue in the monthly video conf on Monday. >>>>=20 >>>> I will comment out cdrkit in my make.sh so I can check out if the = other packages that use cmake (12 of them) can all be made to work with = the latest cmake. >>>>=20 >>>> Regards, >>>>=20 >>>> Adolf.