On 24. 09. 20, 21:38, Luc Van Oostenryck wrote:
> On Mon, Sep 21, 2020 at 09:44:00AM +0200, Christian Eggers wrote:
>> Hi Luc,
>>
>> On Thursday, 17 September 2020, 16:20:17 CEST, Luc Van Oostenryck wrote:
>>> On Thu, Sep 17, 2020 at 01:08:57PM +0200, Christian Eggers wrote:
>>>> Build of the current linux kernel breaks on my system due to segmentation
>>>> fault when running sparse.
>>>>
>>>> Sparse version: 0.6.2 (built by openSUSE build service)
>>>
>>> Hi,
>>>
>>> This has already been reported and fixed in the main tree in late July.
>>> It's not clear to me if the latest OpenSUSE packages for sparse contain
>>> or not the needed fix.
>>>
>>> Can you try the version compiled from the source? It's super-easy:
>>> cd $dir
>>> git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
>>> cd sparse
>>> make
>>> cp sparse ~/bin/
>>>
>>
>> I fetched the source RPM from openSUSE and replaced the 0.6.2 tar.xz with the
>> current master. After building an updating the RPM, sparse doesn't crash
>> anymore.
>>
>> openSUSE ships two versions of sparse [1]:
>> - official release: 20180324
>> - experimental: 0.6.2
>>
>> It seems that both version are affected from this problem. The "experimental"
>> version should be automatically updated after a new version of sparse is
>> released. The "official release" will probably only accept patches resolving
>> specific problems. If you can provide a patch against 20180324, I would try to
>> write a bug report against the openSUSE package. This could save some time for
>> the next person stumbling over this problem... If you provide the commit id,
>> openSUSE can also decide themself whether to fix or upgrade the current
>> version.
>
> In the official tree, there is a branch 'maint-v0.6.2' which just contain
> 4 patches fixing some problems with the release v0.6.2, the second patch
> 77f35b796cc8 ("generic: fix missing inlining of generic expression")
> being the one fixing this problem.
Being fixed in Tumbleweed:
https://build.opensuse.org/request/show/837254
If you want the fix on older distros, we can do that, but you have to
create a bug against the product first… 20180324 is pretty old version
and is both in 15.1 and even 15.2.
thanks,
--
js
