From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: [PATCH] boost: Fix rootfile for x86_64 Date: Tue, 07 Jun 2022 16:39:47 +0000 Message-ID: In-Reply-To: <71654c41-b49c-581b-4978-b144f046fd3b@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5427048919105292445==" List-Id: --===============5427048919105292445== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, my only clue on that front would be the GCC update we've had in next the other day. That requires an updated toolchain, I believe, hence a fresh ccach= e. Perhaps it has got something to do with that, but that's just a wild stab in the dark as well. Anyway, it's just "next", so its ugly, but nothing to have headaches on. I am at it and try to work this out. Thanks, and best regards, Peter M=C3=BCller > Hi, >=20 > I'm a bit puzzled, too... >=20 > And I must confess that I hadn't your patch dated 4.5.2022 patch in > mind. I had to search for it after I read your mail. >=20 > I just thought: "If you need it - you can have it..." ;-) >=20 > Best, > Matthias >=20 > On 07.06.2022 13:12, Adolf Belka wrote: >> Interesting. >> This is the same boost patch that I submitted about a month ago but=20 >> didn't work in the IPFire build system, although it did in my personal=20 >> IPFire build. >> >> Now I saw that the nightlies were failing due to the same boost rootfile=20 >> issue that I was seeing on my system and that the merging of the boost=20 >> rootfile change now causes the nightly build to work again. >> >> What I don't understand is why I saw the boost rootfile problem on my=20 >> build but it wasn't seen on the IPFire build system till now. >> >> Still major thing is that it looks to be working and has been=20 >> successfully merged. >> >> Regards, >> Adolf. >> >> On 07/06/2022 08:29, Peter M=C3=BCller wrote: >>> Thank you. :-) >>> >>> Reviewed-by: Peter M=C3=BCller >>> >>>> Signed-off-by: Matthias Fischer >>>> --- >>>> config/rootfiles/common/x86_64/boost | 12 ++++++------ >>>> 1 file changed, 6 insertions(+), 6 deletions(-) >>>> >>>> diff --git a/config/rootfiles/common/x86_64/boost b/config/rootfiles/com= mon/x86_64/boost >>>> index 357dc2d1d..fe77e6f8c 100644 >>>> --- a/config/rootfiles/common/x86_64/boost >>>> +++ b/config/rootfiles/common/x86_64/boost >>>> @@ -16096,8 +16096,8 @@ >>>> #usr/lib/cmake/boost_python-1.76.0 >>>> #usr/lib/cmake/boost_python-1.76.0/boost_python-config-version.cmake >>>> #usr/lib/cmake/boost_python-1.76.0/boost_python-config.cmake >>>> -#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-mt-x64-share= d-py3.8.cmake >>>> -#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-x64-shared-p= y3.8.cmake >>>> +#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-mt-x64-share= d-py3.10.cmake >>>> +#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-x64-shared-p= y3.10.cmake >>>> #usr/lib/cmake/boost_random-1.76.0 >>>> #usr/lib/cmake/boost_random-1.76.0/boost_random-config-version.cmake >>>> #usr/lib/cmake/boost_random-1.76.0/boost_random-config.cmake >>>> @@ -16250,10 +16250,10 @@ usr/lib/libboost_nowide-x64.so.1.76.0 >>>> usr/lib/libboost_prg_exec_monitor-mt-x64.so.1.76.0 >>>> #usr/lib/libboost_prg_exec_monitor-x64.so >>>> usr/lib/libboost_prg_exec_monitor-x64.so.1.76.0 >>>> -#usr/lib/libboost_python38-mt-x64.so >>>> -usr/lib/libboost_python38-mt-x64.so.1.76.0 >>>> -#usr/lib/libboost_python38-x64.so >>>> -usr/lib/libboost_python38-x64.so.1.76.0 >>>> +#usr/lib/libboost_python310-mt-x64.so >>>> +usr/lib/libboost_python310-mt-x64.so.1.76.0 >>>> +#usr/lib/libboost_python310-x64.so >>>> +usr/lib/libboost_python310-x64.so.1.76.0 >>>> #usr/lib/libboost_random-mt-x64.so >>>> usr/lib/libboost_random-mt-x64.so.1.76.0 >>>> #usr/lib/libboost_random-x64.so >> >=20 --===============5427048919105292445==--