Displaying 4 results from an estimated 4 matches for "__libdir".
Did you mean:
_libdir
2006 Dec 02
1
How to install rkhunter properly
...khunter-1.2.8.tar.gz
* mv /root/etc_rpm_platform /etc/rpm/platform
* rpm -ivh /usr/src/redhat/RPMS/noarch/rkhunter-1.2.8-1.noarch.rpm
* wget http://prdownloads.sourceforge.net/rkhunter/hashupd.sh?download
* chmod +x hashupd.sh
* ./hashupd.sh
In general I had 2 problems:
* On my 64 bit machine, the __libdir was set to /usr/lib64 whereas
rkhunter uses an ugly "/usr/lib"
(solved with moving the platform file temporarily)
* rkhunter -c showed me all the binaries in /bin /sbin/ and /usr/bin as
'bad'.
(solved with downloading and calling ./hashupd.sh)
HTH
cu - Michael
--
Michael...
2020 May 14
2
R 4.0.0
...to do that, and will prevent breakages and complaints.
Something that I have been wondering for some time, previous to this thread,
is why is not this the default also for system installation and not just for
users installs.
With this I mean to have the system directories to be respectively:
%{__libdir}|%{__datadir}/R<major>.<minor>
Is this due to inertia or are there other reasons. That would naturally solve
the need to rebuild for each minor release. The major point here is that would
apply not only to our packages but also for others installed using R itself.
Best regards,
--...
2020 May 14
0
R 4.0.0
...ges and complaints.
>
> Something that I have been wondering for some time, previous to this thread,
> is why is not this the default also for system installation and not just for
> users installs.
>
> With this I mean to have the system directories to be respectively:
>
> %{__libdir}|%{__datadir}/R<major>.<minor>
>
> Is this due to inertia or are there other reasons. That would naturally solve
> the need to rebuild for each minor release. The major point here is that would
> apply not only to our packages but also for others installed using R itself.
M...
2020 May 11
3
R 4.0.0
Hmmm. That seems like a rather heavy dependency, given that I think we've
only been forced to do rebuilds for everything as a result of 4.0.0 and
3.4.0.
Does anyone know if upstream has any sort of commitment to ABI here that we
could depend on (e.g. only breaking on major versions, never minor) ?
Tom
On Sat, May 9, 2020 at 5:32 AM I?aki Ucar <iucar at fedoraproject.org> wrote:
>