Blake Michaleski
EF4
have fun.....
After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.
I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.
For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.
From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.
Sincerely, Jeff D.
Originally posted by Eric Whitehill
You need to do a couple of things first.
It looks like configure is farking out on you, so you need to do the following:
in /rdss/soloii110/
rm config.cache
make clean
And then when that is done, since libncurses isn't installed by default IIRC....
You should be able to do a ln -sf /lib/libncurses.so.5.0 /lib/libcurses.so and I think that'll correct the issue with libncurses not showing up. (if you can't do a 'locate libcurses' and find anything, then you may need to install libncurses which you can do from package or .rpm or compile by hand if you're really daring)
If this machine is publically accessable, I wouldn't mind digging in and seeing if I can get it going.
-Eric
Originally posted by Blake Michaleski+--><div class='quotetop'>QUOTE(Blake Michaleski)</div><!--QuoteBegin-Eric WhitehillYou need to do a couple of things first.
It looks like configure is farking out on you, so you need to do the following:
in /rdss/soloii110/
rm config.cache
make clean
linux:/rdss/soloii110 # rm config.cache
rm: cannot remove `config.cache': No such file or directory
linux:/rdss/soloii110 # make clean
for d in translate editor perusal; do
(cd $d; make clean)
done
make[1]: Entering directory `/rdss/soloii110/translate'
rm -f core *.o *~ xltrsii ddex to_fb nx_reblock libs2.a
make[1]: Leaving directory `/rdss/soloii110/translate'
make[1]: Entering directory `/rdss/soloii110/editor'
rm -f core *.o *~ "" libsoloedit.a
make[1]: Leaving directory `/rdss/soloii110/editor'
make[1]: Entering directory `/rdss/soloii110/perusal'
rm -f core *.o *~ soloii ""
make[1]: Leaving directory `/rdss/soloii110/perusal'
libncurses couldntbe found on the suse dvd. does it need to be obtained on the net.
bte im posting this reply from the linux machine.[/b]
Originally posted by rdewey
Does SuSE have "yum"? In Fedora Core, you could simply issue the command "yum install xdevel" and it would automatically install the latest version in addition to all of the dependencies straight from the internet.