No, disregard that. That's not it. -_-

On 29 May 2018 at 17:23, Jiří Zárevúcky <[email protected]> wrote:
> So, the issue seems to be that the toolchain builds executables with
> dynamic relocations, which isn't supported on most platforms.
>
> I'll commit a workaround as soon as I finished checking it works.
>
> -- jzr
>
> On 29 May 2018 at 08:17, Vojtech Horky <[email protected]> wrote:
>> Hello,
>>
>> it seems that some recent changes caused that harbours are being built
>> (well, most of them) but once they are executed, they dereference a
>> null pointer.
>>
>> Logs are available in build 180 [1] and it is possible to download an
>> ISO image with GCC to test [2]. I tried in QEMU and even 'gcc
>> --version' did not work.
>>
>> [1] http://ci.helenos.org/build-180/
>> [2] http://ci.helenos.org/build-180/amd64/helenos-amd64-with-gcc.iso
>>
>> Because build 179 was okay, the issue is probably caused by changes on
>> May 25. I suspect the "Don't use custom ldscripts in uspace. (#38)"
>> (BTW, the period should not be there ;-)) [3] as that was the only
>> system-wide change.
>>
>> [3] 
>> https://github.com/HelenOS/helenos/commit/a05ec6671002c451fceb01aa0ab3f71f004efb6d
>>
>> Would someone, please, re-test that this is reproducible and is not a
>> CI-only problem.
>>
>> Thanks,
>> - Vojta
>>
>> _______________________________________________
>> HelenOS-devel mailing list
>> [email protected]
>> http://lists.modry.cz/listinfo/helenos-devel

_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel

Reply via email to