On 02/26/2015 10:31 AM, Gordan Bobic wrote:
> On 2015-02-25 23:32, Jacco Ligthart wrote:
>> Hi,
>>
>> Gordan notified me that he was unable to start X on his chromebook with
>> RSEL6 (segfault)
>>
>> I dug a bit into that and narrowed it down to the pixman package.
>>
>> I am still not sure what the issue really is, but discovered that
>> installing pixman from RSEL7 fixed the issue. The RSEL7 version is
>> slightly older (it has one patch less). So for anybody else with this
>> issue the following command should fix this:
>>
>> $ sudo yum downgrade pixman
>>
>> At first I thought that the extra patch was the issue, but building
>> pixman without it still resulted in the segfault.
>> I look at this as more a workaroud than a fix, but it works :)
>
> I am wondering if this has to do with gcc. I seem to recall that
> your test updates repository includes a version of gcc that is
> newer than what is in the main repository.
>
> A while back when I was testing this, I found that the newer
> version of gcc builds and mostly works, but resulted in some
> binaries being broken and segfaulting.
>
> If you are building your packages with this newer gcc, could this
> be one of the manifestations of gcc issues? I just looked through
> the patchset differences, and the 4.4.5 version includes an extra
> libgcc patch which appears to be omitted in 4.4.7. Do you know if
> this has been rolled into the 4.4.7 base? I'm wondering if it
> might still be needed, even if the original patch no longer
> applies cleanly.
>
> I'm purely going on the fact that if the source of the package is
> the same, the root cause of the problem must be either in another
> library being linked against or in the compiler.
>
I was thinking in the same direction, but thought "kernel-headers"
although I do not understand how pixman would depend on that.

as for the 4.4.5 (libgcc_post_update -> lua)  patch, yes that was rolled
into 4.4.7 base. In 4.4.5 you disabled "Source1". This Source is not
present in 4.4.7 to start with.

Jacco
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to