public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] boost: Fix rootfile for x86_64
Date: Tue, 07 Jun 2022 13:12:32 +0200	[thread overview]
Message-ID: <c2c2f168-7a4c-e8ed-a3f6-f86ba3c3d949@ipfire.org> (raw)
In-Reply-To: <50274004-f018-2c17-9d7b-9381b0cfa5c0@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2661 bytes --]

Interesting.
This is the same boost patch that I submitted about a month ago but 
didn't work in the IPFire build system, although it did in my personal 
IPFire build.

Now I saw that the nightlies were failing due to the same boost rootfile 
issue that I was seeing on my system and that the merging of the boost 
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 
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 
successfully merged.

Regards,
Adolf.

On 07/06/2022 08:29, Peter Müller wrote:
> Thank you. :-)
>
> Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>>   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/common/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-shared-py3.8.cmake
>> -#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-x64-shared-py3.8.cmake
>> +#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-mt-x64-shared-py3.10.cmake
>> +#usr/lib/cmake/boost_python-1.76.0/libboost_python-variant-x64-shared-py3.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

-- 
Sent from my laptop


  reply	other threads:[~2022-06-07 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 17:04 Matthias Fischer
2022-06-07  6:29 ` Peter Müller
2022-06-07 11:12   ` Adolf Belka [this message]
2022-06-07 15:55     ` Matthias Fischer
2022-06-07 16:39       ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c2c2f168-7a4c-e8ed-a3f6-f86ba3c3d949@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox