<div dir="ltr">Wait, why are you asking for help with salix packages on the SBo mailing list?</div><br><div class="gmail_quote"><div dir="ltr">On Wed, May 2, 2018 at 2:47 PM Didier Spaier <<a href="mailto:didier@slint.fr">didier@slint.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Today someone nicknamed Jardenblack posted this in a Salix forum:<br>
[quoted post]<br>
Here is a list of packages that have bad soft links and need to be fixed:<br>
fvwm95-2.0.43f-i486-2salix<br>
HawkNL-1.68-i486-1salix<br>
http-parser-2.7.1-i486-1salix<br>
libiptcdata-1.0.4-i486-2salix<br>
oss-4.2.2011-i586-1salix<br>
PDCurses-3.4-i486-1salix<br>
qt3-3.3.8b-i486-5salix<br>
<br>
example of the problem:<br>
( cd usr/lib ; ln -sf /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so libXpanel.so )<br>
<br>
I found this problem searching thur the /var/log/scripts files. I hope this helps.<br>
[/quoted post]<br>
<br>
I couldn't answer because for an unknown reason the thread and the user<br>
disappeared.<br>
<br>
However I had a look at two cases and confirm the issue.<br>
For PDCurses the wrong links are mad by by install target in Makefile.in<br>
in the source archive as shown below<br>
install:<br>
<lines removed><br>
ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \<br>
$(libdir)/$(SHLPRE)Xpanel$(SHLPST)<br>
ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a<br>
-$(RANLIB) $(libdir)/libXpanel.a<br>
For fvwm95 the wrong link comes from the install target in<br>
sample.fvwmrc/Makefile.in in the source archive as sown below:<br>
install: <br>
${INSTALL_DATA} ${RC} ${fvwm_dir} <br>
${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc}<br>
(LN is converted to ln -s during the build)<br>
<br>
I was too lazy to check the other packages (I don't use any of those<br>
listed by Jardenblack)<br>
but I assume that other packages have a similar issue, i.e. symlinks<br>
from a file in the build dir that will be broken as soon as the build<br>
dir is removed.<br>
<br>
Maybe the broken symlinks do not always hurt but still, a systematic<br>
check that the symlinks (in install/doinst.sh or /var/log/scripts) will<br>
survive the removal of the build dir could be useful?<br>
<br>
Best,<br>
<br>
Didier <br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>