Menu
▾
▴
#53 nsis 204 install.sh installation under Linux
The stable NSIS version 204 fails to properly install
under Linux. This patch solves the installation issues
and adds NSIS library path the the dynamic loader
cache configuration. For instance when installing in
"/usr/local" the installscript produces the file
/etc/ld.so.conf.d/nsis.conf . The contents of that
script is: "/usr/local/lib/NSIS" and the program
/sbin/ldconfig should be run afterwards.
Logged In: YES
user_id=584402
No patch is attached, please try again. Don't forget to
check the checkbox.
Logged In: YES
user_id=518287
Oops. Patch attached
Logged In: YES
user_id=584402
The DIRS problems was already fixed in the latest CVS version.
Why did you change $(tempfile) to "tmp_nsis.sh"?
Why does ld need to know about the location of NSIS?
makensis doesn't use any loadable objects from that directory.
Logged In: YES
user_id=518287
You are right LD does not need to know the path to NSIS. I
assumed it would because it installed in a library directory.
Maybe a /usr/share/NSIS should be better a better choice.
I changed $(tempfile) because it was undefined on my FC3
Linux system. The installation exited at that empty variable.
Logged In: YES
user_id=584402
lib is indeed a weird place to put NSIS. I'll change it.
It seems $(tempfile) is a feature of bash. What is /bin/sh
linked to on your FC3?
Logged In: YES
user_id=518287
/bin/sh is linked to bash on Fedora Core 3
[jpsaman@somepc ~]$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Feb 15 12:19 /bin/sh -> bash
${tempfile} is by default empty.
[jpsaman@somepc ~]$ echo ${tempfile}
It might be less error prone if you used the name of the
final destination script before installing it on the right
place.
Logged In: YES
user_id=584402
OK, changes made in latest CVS version.
But I'd still like to know, out of curiosity, why
$(tempfile) doesn't work. Can you try it again, only with
parenthesis instead of curly brackets? The script itself
uses parenthesis.
Logged In: YES
user_id=518287
Parenthesis or curly brackets don't make a difference,
$(tempfile), $(TMPFILE), $(TEMPFILE) are not defined. I
checked on FC1 and FC3. You could use the utility mktemp
to create a filename, that is available on Linux systems
AFAIK.
Logged In: YES
user_id=518287
Parenthesis or curly brackets don't make a difference,
$(tempfile), $(TMPFILE), $(TEMPFILE) are not defined. I
checked on FC1 and FC3. You could use the utility mktemp
to create a filename, that is available on Linux systems
AFAIK.