Possible... esp w/ raptor that saw a huge bump from 1.x to 2.x... 

> On Oct 27, 2020, at 6:47 PM, Don Lewis <truck...@apache.org> wrote:
> 
> On 27 Oct, Jim Jagielski wrote:
>> Maybe... but it DID WORK before. That is, before the mega patch,
>> configure did the "right thing". So if something is causing configure
>> to make a different decision, it is due to the interaction w/ the new
>> stuff that the RDF stuff does. The problem is with the patch or how it
>> is working...
> 
> I'm thinking of any configure scripts used by raptor / rasqal / redland,
> which would have changed by the upgrade.
> 
>> In any case, iirc we did compare the config.log files between 4.1.7
>> and 4.1.8-RC2 and there was no pertinent difference between the 2...
>> 
>>> On Oct 27, 2020, at 5:24 PM, Don Lewis <truck...@apache.org> wrote:
>>> 
>>> On 27 Oct, Jim Jagielski wrote:
>>>> For completeness, and especially for those not following the thread,
>>>> what we have conclusively shown is that it is NOT an issue w/ the
>>>> build server, which is the same we've been using for several 4.1.x
>>>> releases, nor with the configure and build parameters (also
>>>> unchanged from previous). It is this mega patch which combines
>>>> several upgrades in one large patch.
>>>> 
>>>> My thought is that w/ the change with the RDF libs, the patch either
>>>> pulls in the wrong library (maybe the system library) for something,
>>>> which causes issues w/ newer distros, or else it doesn't pull in a
>>>> library and the one used by newer distros causes the problem.
>>> 
>>> Or maybe a configure script makes a different decision about the
>>> system libraries on CentOS 5 (vs when building on something newer)
>>> that causes the code not to work properly on newer distros.
>>> 
>>>>> On Oct 27, 2020, at 5:09 PM, Jim Jagielski <j...@jagunet.com> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Oct 27, 2020, at 2:34 PM, Don Lewis <truck...@apache.org> wrote:
>>>>>> 
>>>>>> On 27 Oct, Jim Jagielski wrote:
>>>>>>> Thanks all... I am now building the final 'git bisect' test,
>>>>>>> based on
>>>>>>> 
>>>>>>> https://github.com/apache/openoffice/commit/f7070ae3689d0d34bf9dab3d31f56744d0df4784
>>>>>>> 
>>>>>>> assuming that this is good, it seems like 99% likely that the
>>>>>>> problem arose with
>>>>>>> 
>>>>>>> https://github.com/apache/openoffice/commit/e9fab906a0063dca04a52bfc5270c9d70ccbbb27
>>>>>>> 
>>>>>>> the raptor / rasqal / redland mega patch. Which of those 3 is
>>>>>>> unknown, but a quick look over seems to indicate that the raptor
>>>>>>> upgrade was the most significant of the 3, but the redland patch
>>>>>>> also seems to have some weird things (like no longer linking
>>>>>>> openssl or libltdl) so who knows :/
>>>>>> 
>>>>>> Questions (which may be related):
>>>>>> 
>>>>>> Why does this only affect AOO418 and not AOO42X and trunk?
>>>>>> 
>>>>>> Why does this only seem to affect builds done on CentOS 5 and run
>>>>>> on a newer distro and not when run on CentOS 5 and not when
>>>>>> compiled on a newer distro?
>>>>> 
>>>>> If I knew those answers we wouldn't be wondering what is going on
>>>>> and I wouldn't have had to create >15 test builds :-)
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>> <mailto:dev-unsubscr...@openoffice.apache.org> For additional
>>>>> commands, e-mail: dev-h...@openoffice.apache.org
>>>>> <mailto:dev-h...@openoffice.apache.org>
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> <mailto:dev-unsubscr...@openoffice.apache.org 
>>> <mailto:dev-unsubscr...@openoffice.apache.org>> For additional
>>> commands, e-mail: dev-h...@openoffice.apache.org 
>>> <mailto:dev-h...@openoffice.apache.org>
>>> <mailto:dev-h...@openoffice.apache.org 
>>> <mailto:dev-h...@openoffice.apache.org>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> <mailto:dev-unsubscr...@openoffice.apache.org>
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> <mailto:dev-h...@openoffice.apache.org>

Reply via email to