Re: [Trustedqsl-testing] OpenSSL 3.0.0

[Rick M. <k1...@ar...>]

On Wed, Dec 8, 2021 at 8:37 AM Richard Shaw <hob...@gm...> wrote:

> On Sun, Dec 5, 2021 at 3:23 PM Rick Murphy <k1...@ar...> wrote:
>
>> On Sun, Dec 5, 2021 at 3:16 PM Richard Shaw <hob...@gm...> wrote:
>>
>>> On Sun, Dec 5, 2021 at 2:10 PM Rick Murphy <k1...@ar...> wrote:
>>>
>>>> Yes, this builds on MacOS, Windows. and Linux. It also builds on
>>>> Debian, Fedora, Ubuntu, .... building and installing is distinct from
>>>> building to conform to a distribution's policies.
>>>>
>>>> For example, I stopped bundling a minimal trusted certificate store
>>>> (ca-bundle.crt) on Unix builds because some distro forbade that.
>>>>
>>>> This issue with the RPATH setup in the CMakeLists.txt file is a patch
>>>> that was submitted to correct a problem with some distro that doesn't use
>>>> "/lib64" as I recall.  This is essentially me accepting changes that work
>>>> well for a single distribution and not working in a way to adapt to a wide
>>>> range of distro and distro ages, along with the fact that I'm not an expert
>>>> in how to build this portably.
>>>>
>>>
>>> How long ago was it contributed? CMake handles RPATH pretty well these
>>> days and should remove RPATH on install when installing into system
>>> locations, or otherwise update it.
>>>
>>
>> A long while ago. These changes are in TQSL 2.1 - circa 2015. Perhaps
>> earlier.
>>
>> I'm happy to accept help here with cleaning this up, as it seems over
>> time that this has become overcomplicated in a way that CMake is probably
>> able to do a much better job at, versus the current ad-hoc attempts.
>>
>
> Sounds good to me, How do you propose we test? Obviously Fedora is OK and
> by extension RHEL and derivatives as I build for Fedora EPEL as well.
>

[Sorry, this draft apparently has been stalled for some time unsent,[

I accepted the patches here, removed the RPATH setting, removed the setting
for library path, and added an include for GNUInstallPaths, all of which I
assumed would make this a distribution responsibility.

Built a tar.gz and started down my list of VMs running various Linux
distributions.

The VERY FIRST TRY failed. CentOS 7, It installed libtqsllib.so into
/usr/local/lib/  and tqsl couldn't be activated because that library could
not be found (worked when moved to /lib64).

I'm still asking for help here.  People seem to be implying that including
GNUInstallPaths just fixes these library dependent issues, but I'm not sure
what to do when trying this runs right into an error.


> I'm unfamiliar with how tqsl development is managed. Is there any infra
> where CI is performed? Known group of "testers"?
>

That question is kind of interesting. There is one developer, who is me.
There's only one person who has ever provided me feedback on test releases
(that is the purpose of this mailing list.)
I have a fairly complete set of regression testing scripts for the command
line operations, but I have no experience with building test harnesses for
a multi-platform gui-driven UI.  Any help here would be quite welcome.

73,
    -Rick
-- 
Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA