As a workaround, you can run the application with LinuxThreads, i.e.
LD_ASSUME_KERNEL=2.4.1 /opt/rational//releases/rose.2003.06.00/i386_linux2/bin/rjavarelay options
I made a script setting the variable, running the rose startup script and finally removing the variable again. I guess any program started while Rose is running would also be using the older libraries, but that is OK, or isn't it..?
It is always better to only set it for the exact program that needs it.
In fact, if you do it as originally laid out on one line:
LD_ASSUME_KERNEL=2.4.1 /path/to/rjavarelay options
.. then it *is* only set for that program; your script need only have that line and the #!/bin/bash header.
If you *do* set it as a var. in a script:
#!/bin/bash export LD_ASSUME_KERNEL=2.4.1 /path/to/rjavarelay options
.. it'll *still* only apply to that app. as the value is set only for the script, not the caller or any other process.
-- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit
