discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Porting GNUstep to the RISC-V architecture


From: Frederik Seiffert
Subject: Re: Porting GNUstep to the RISC-V architecture
Date: Fri, 13 May 2022 10:42:08 +0200

I tested the Make changes with the MSVC toolchain and it works fine.

Frederik


> Am 10.05.2022 um 23:13 schrieb Fred Kiefer <FredKiefer@gmx.de>:
> 
> I committed both changes together to a tools-make branch. Somebody now has to 
> check whether this still works with MSVC as config.guess seem to have dropped 
> support for that platform. As far as I can tell we currently don’t have any 
> CI pipeline set up for make. This is probably tested when building base.
> Frederik, could you please have a look?
> 
> Cheers,
> Fred
> 
>> Am 08.05.2022 um 22:49 schrieb lars.sonchocky-helldorf@hamburg.de:
>> 
>> Hi Fred,
>> 
>> I did this change only in tools-make but then again I’ve built the whole 
>> GNUstep hierarchy at once using that compile-all script from tools-scripts. 
>> So I guess it might be different if you’re building those modules 
>> separately. I think it wouldn’t hurt to update the config.guess and the 
>> config.sub everywhere just to be safe.
>> 
>> kind regards,
>> 
>>      Lars
>> 
>>> Am 08.05.2022 um 22:24 schrieb Fred Kiefer <fredkiefer@gmx.de>:
>>> 
>>> OK, so I will undo my local change and instead update these two files. Was 
>>> that change needed for all GNUstep modules?
>>> 
>>> Fred
>>> 
>>>> Am 08.05.2022 um 05:15 schrieb lars.sonchocky-helldorf@hamburg.de:
>>>> 
>>>> From sheer excitement I forgot to answer your question: configure works 
>>>> fine so far even when not updating configure and configure.ac, e.g. 
>>>> replacing config.guess and config.sub with recent versions is just enough.
>>>> 
>>>> regards,
>>>> 
>>>>    Lars
>>>> 
>>>>> Am 08.05.2022 um 01:11 schrieb Fred Kiefer <fredkiefer@gmx.de>:
>>>>> 
>>>>> Lars,
>>>>> 
>>>>> could you please try whether it would be sufficient to just replace these 
>>>>> two file without updating configure and configure.ac?
>>>>> That update is fine for me, but it would stop people with an old autoconf 
>>>>> to regenerate the configure file.
>>>>> 
>>>>> Cheers,
>>>>> Fred
>>> 
>> 
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]