[netsurf-dev] Re: Toolchain build for AmigaOS4

On 08/11/2024 10:48, Chris Young wrote:
>
>
>
> On 07/11/2024 10:56, Chris Young wrote:
>>
>>
>> On 06/11/2024 13:09, vincent sanders wrote:
>>>
>>> On 18/10/2024 15:09, Chris Young wrote:
>>>> Hi all
>>>>
>>>> I've had some issues this year with various things not working, and
>>>> tracked it down to the OS4 betas and (indirectly) the update of the
>>>> SDK.  There were two problems;
>>>> 1. DNS resolution was not working.  I fixed this at the start of
>>>> the year but after fixing (2) it broke again in a different way.
>>>> I've temporarily disabled the threaded resolver until I can find a
>>>> more permanent solution.
>>>> 2. SSL/TLS sites were not opening.  I'm not sure why but it may be
>>>> the same problem as OS3 was having with OpenSSL.  As AmiSSL is kept
>>>> up-to-date now, unlike when I started porting NetSurf, I've
>>>> switched the OS4 build over to using AmiSSL.
>>>>
>>>> Please can somebody check and merge my chris/amissl-os4 branch into
>>>> toolchains, and rebuild the ppc-amigaos toolchain?
>>>> The equivalent chris/amissl-os4 branch can then be merged into
>>>> NetSurf and the CI builds should be working again on OS4 beta.
>>>>
>>>> Thanks!
>>>> Chris
>>>>
>>>>
>>> hi chris, apologies for the delay. I applied a variant on your
>>> changes to the toolchain (selecting the ssl provider suppresses
>>> openssl so some changes you had were not required)
>>>
>>> I also updated the c-ares version which may help with the DNS issues
>>> (maybe)
>>>
>>> You should be ok to merge any netsurf changes you want now
>>>
>>>
>> Fab, thanks.  I'll try with the new c-ares - it looked like the issue
>> was that it didn't have the code for obtaining DNS servers in it
>> (which I added), but it still didn't work.  Maybe I did something
>> wrong, I'll try again.
>>
>
> Well, this is a bit weird.  After all the updates I'm now getting
> "unsupported protocol", even from the Curl executable.  It shows http
> and https in the list but neither are working :(
>
>
I updated the SDK with up to date versions of most libraries (including
libcurl) and re-built the CI toolchains. This was actually because I was
hoping to do a release this month amd we were behind on security updates

Maybe this will help? unsure why building libcurl with a different ssl
library would cause the protocol failures you see though.