On Mon, 29 Dec 2025 13:21:19 +0000, in gmane.os.cygwin you wrote:

>On 29/12/2025 09:56, Mark Geisert via Cygwin wrote:
>> Replying to myself once again...
>> 
>> On 12/14/2025 4:41 PM, Mark Geisert via Cygwin wrote:
>>> Hi Marco,
>>>
>>> On 12/11/2025 6:27 AM, Marco Atzeri via Cygwin wrote:
>>>> On 06/12/2025 05:54, Mark Geisert wrote:
>>>>> The following packages have been uploaded to the Cygwin distribution:
>>>>>
>>>>> * libQt5Core5-5.15.18-1
>>>>> * libQt5Core-devel-5.15.18-1
>>>>> * libQt5Sql5-5.15.18-1
>>>>> * libQt5Sql-devel-5.15.18-1
>>>>> * libQt5Gui5-5.15.18-1
>>>>> * libQt5Gui-devel-5.15.18-1
>>>>> * qt5-base-doc-5.15.18-1
>>>>> * qt5-base-examples-5.15.18-1
>>> [...]
>>>> Thanks Mark,
>>>>
>>>> unfortunately both doxywizard and octave need something more
>>>> and mixed versions seem to not work.
>> [...]
>>>
>>> It turns out both doxywizard and oxygen are dependent on a 5.15.18 
>>                                     ^^^^^^
>>                                     octave, oops
>>> libQt5Svg.dll.  It's a secondary reference.  I'm working on a build 
>>> for that and whatever tertiary references that uncovers.  Might take 
>>> time.
>> 
>> I've tested both programs with my own 5.15.18-1 libQt5Svg-5.dll 
>> successfully.  There was a hiccup in that both provoke a SIGSEGV in an 
>> internal Qt5 memory fill function that uses avx2 cpu instructions.  When 
>> I rebuilt qt5-base with flags to turn that usage off, the resulting 
>> 5.15.18-2 qt5-base DLLs allow both programs to launch to idle state.
>> 
>> The qt5-base DLLs have been updated to -2 and uploaded, still as test 
>> versions.  The qt5-svg DLL upload (also is a test version) is awaiting a 
>> permission change when jturney has a chance.
>
>Done.
>
>Sorry, but I think this is a mandatory gold star!
>
>Thanks!

Awarded! https://cygwin.com/goldstars/#MG

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

Reply via email to