[Scons-users] scons-4.3.0 bug reading scons-3.1.2 generated .sconsign.dblite

[Jay West]

Actually, the workaround isn't sufficient.  We also need to delete all the
other versions of .sconsign.dblite* as they will be out of date.

Jay


On Sun, Mar 20, 2022 at 6:58 PM Jay West <jhdub23 at gmail.com> wrote:

> If scons did a full rebuild, it would not be a problem.  The issue is that
> scons does NOT do a full rebuild, thinking that targets were up to date
> when they were really not.
>
> I see a workaround that someone else took:
> https://github.com/Autodesk/arnold-usd/pull/116/commits/a404d5f3400437beb4bad561ef1811538f7af022.
> I will be putting this into our SContruct file.  Can this be made the
> default behavior?
>
> Thanks,
>
> Jay
>
>
> On Sat, Mar 19, 2022 at 11:09 AM Bill Deegan <bill at baddogconsulting.com>
> wrote:
>
>> Switching from py2.7 -> py 3.5 invalidates the .sconsign files contents.
>> You have to do a full build when you make that switch.
>> It's in the release notes somewhere.
>>
>> https://scons.org/scons-300-is-available.html
>>
>> There's no way around it.
>> The best you can do is name your SConsign file to include the python
>> version so at least they won't be invalid when you switch from one to
>> another, but you will see additional rebuilds which may not be strictly
>> necessary.
>>
>> -Bill
>>
>> On Fri, Mar 18, 2022 at 5:03 PM Jay West <jhdub23 at gmail.com> wrote:
>>
>>> Yes, our scons-3.1.2 was using python-2.7.17, and our scons-4.3.1 is
>>> using python-3.9.10.  We get a pickling error when trying to run
>>> scons-3.1.2 after scons-4.3.1 which is good.  Running scons-4.3.1 after
>>> scons-3.1.2 runs without error, but results in bad builds, which is
>>> terrible.
>>>
>>>
>>> On Fri, Mar 18, 2022 at 3:04 PM Bill Deegan <bill at baddogconsulting.com>
>>> wrote:
>>>
>>>> Sounds like you also switched from python 2.7 to python 3.5 or higher?
>>>>
>>>> On Fri, Mar 18, 2022 at 2:07 PM Jay West <jhdub23 at gmail.com> wrote:
>>>>
>>>>> We are migrating from scons-3.1.2 to scons-4.3.0 and have encountered
>>>>> incorrect builds.
>>>>>
>>>>> After building with scons-3.1.2, changing some files, and then running
>>>>> scons-4.3.0, it appears that scons-4.3.0 cannot read some dependencies from
>>>>> the DB file.  Instead of error'ing out or ignoring the DB file, it happily
>>>>> generates an incorrect build.  However, running:
>>>>>
>>>>> sconsign .sconsign.dblite
>>>>>
>>>>>
>>>>> gives
>>>>>
>>>>> TypeError: '<' not supported between instances of 'str' and 'bytes'
>>>>>
>>>>>
>>>>> Has anyone seen this issue?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jay
>>>>>
>>>>> _______________________________________________
>>>>> Scons-users mailing list
>>>>> Scons-users at scons.org
>>>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>>>
>>>> _______________________________________________
>>>> Scons-users mailing list
>>>> Scons-users at scons.org
>>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>>
>>> _______________________________________________
>>> Scons-users mailing list
>>> Scons-users at scons.org
>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20220320/10901358/attachment.htm>