On 04/08/2018 12:21 AM, David Spencer wrote:
As I want to submit those slackbuilds once finished to slackbuilds.org, what
could be an acceptable solution to fix the lib issues ?
You'll want to coerce the packages to install to the system directories
of lib/lib64. Sometimes one will need to w
>> As I want to submit those slackbuilds once finished to slackbuilds.org, what
>> could be an acceptable solution to fix the lib issues ?
>
> You'll want to coerce the packages to install to the system directories
> of lib/lib64. Sometimes one will need to work with upstream to
> accomplish this
* On 2018 07 Apr 09:27 -0500, nico wrote:
> I could copy libs to a proper directory, makes symlinks or edit
> /etc/ld.so.conf .
I added /usr/local/lib for locally compiled stuff (mostly as a test for
the generic install location for upstream packages I maintain) so that
'ldconfig' will add lib
On Sat, Apr 7, 2018, 10:26 AM nico wrote:
> Hello !
>
> Bit of context first:
> I try to create a slackbuild script for dublin-traceroute (
> https://github.com/insomniacslk/dublin-traceroute ) which depends on
> libtins ( https://github.com/mfontanini/libtins )
>
> The cmake-template for slackbu
Gonna take a shot in the dark here (never used Cmake) but..
I'm assuming you can set the output directory of libraries to
/usr/local/lib64 somewhere in there. This person seems makes it sound
like it needs coercion:
https://cmake.org/pipermail/cmake/2013-July/055374.html
but that's a pretty
Hello !
Bit of context first:
I try to create a slackbuild script for dublin-traceroute (
https://github.com/insomniacslk/dublin-traceroute ) which depends on
libtins ( https://github.com/mfontanini/libtins )
The cmake-template for slackbuilds is doing a good job - and I got the
package libt
