Hi Erico,
thank you very much for your information and insights!
On 15.03.2016 20:06, Erico Mendonca wrote:
... cut ...
>> Maybe a question or two?
>>
>> * "PREFIX=/usr/local" on Linux: do you know whether one can rely that by
>> default the major Linux
>> distirbutions also honor "/usr/local/bin" (PATH; it seems that
>> "/usr/local/bin" is defined on
>> PATH), "/usr/local/sbin", "/usr/local/share", etc.
> Yes, by default /usr/local it is defined in all Linux distros, and is also
> present in the PATH. Originally in Unix this tree was reserved for “locally
> compiled binaries”. GNU Autotools-based (automake/autoconf) programs always
> default to /usr/local.
So this would mean, that it is safe to install ooRexx into /usr/local on all
major Linux distros
instead of /usr!
>
>> * "/usr/local/lib" on Linux: do you know whether this directory is defined
>> by default for
>> resolving shared libraries on major Linux distributions? (MacOSX 10.11
>> seems to honor it out of
>> the box.)
>> Otherwise, would defining an entry "/usr/local/lib" in "/etc/ld.so.conf"
>> and then running
>> "ldconf" to update the cache at installation time be an acceptable and a
>> stable solution in your
>> opinion?
> Yes, /usr/local/lib is defined by default on Linux. However, on 64-bit
> systems it’ll default to /usr/lib64 and /usr/local/lib64 for 64-bit
> libraries. /usr/lib and /usr/local/lib are reserved for 32-bit libraries.
> Usually, on RPM-based systems you can find this definition in
> /usr/lib/rpm/macros, in a variable called %_libdir. You can see us using it
> on our SPEC file. RPM takes care of substituting the correct directory.
>
> You can check what your system returns by issuing “rpm —eval ‘%{_libdir}’” .
Wow, thank you very much for this information and insight!!
> As for the ld.so.conf, well that really depends. The most “standard” way
> would be to name ooRexx’s libraries according to the shared libraries naming
> convention (see here:
> http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html),
Super, thank you!
> where the linker name is set along with a version, and ldconfig takes care of
> creating the proper symbolic links when installing the package. Currently,
> ooRexx sends the links “manually” in the package, probably a heritage from
> the OS/2 days (yes, I’m that old). It works, but if need be, you can create a
> file under /etc/ld.so.conf.d and set a new arbitrary search path.
Ha, 1987, OS/2 1.0 without Presentation Manager, 16-bit! Me, too... :)
>> Just a totally unrelated question out of curiosity: the trunk-version of
>> ooRexx (a.k.a. "5.0") got
>> changed to be built with cmake instead of the autoconf tools. Would that be
>> a problem for you (or
>> Perry Werneck for that matter) once an alpha or beta build of it is planned,
>> or are you "fluent" in
>> cmake as well by any chance? :)
>>
> Sure, the Open Build Service supports CMAKE, no problem. I dabble in it, but
> I can learn.. :)
Super, great!
Again, thank you very much for your informative and constructive information!
Best regards,
---rony
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
