# add path'n stuff to ROOT ROOTSYS=/usr/local/root_v4.00.08 export ROOTSYS PATH=$PATH:$ROOTSYS/bin export PATH LD_LIBRARY_PATH=$ROOTSYS/lib/root export LD_LIBRARY_PATHROOTSYS should be pointed to the version of ROOT you want to use. After that you should be able to just say 'rootn.exe'
makedir your_data_dir cd your_data_dir mkdir src bin cd src wget http://www.phy.anl.gov/gs/doc/GSSort/src/src.tgz tar -zxvf src.tgz cp Makefile.Linux Makefile.`uname`.`uname -r` gmake GSSort rootn.exe .L Makefile.Linux .q cd ..now do
rootn.exe .L src/GSUtil_cc.so startsort("bin/GSSort_","c1.chat","c1.log") . . . .
more /etc/auto.homeand they automount as /dk/root1, /dk/root2, etc. If you need some files from the disks of the old suns, you will have to scp them over.
For this reason, the gamuser account on the linux machine
cannot share its home directory with the gamuser account on the
suns, since the gs filer also will not let the linux machine
mount its disks properly.
root  startsort("bin/GSSort_","c1.chat","c1.log") \rm c1.log rm: cannot remove `c1.log': No such file or directory bin/GSSort_ -chat c1.chat > c1.log & Wed Feb 2 10:38:15 CST 2005 xterm -sl 2000 -T c1.log -e tail -f c1.log & Wed Feb 2 10:38:15 CST 2005 Remember to (re)load shared memory mapfile or root file sload("mapfile") or dload("rootfile") root  *** Break *** segmentation violation Generating stack trace... 0x0804b656 inYou might have the "startmapaddress" wrong. Use "sdummyload" to set the proper address. The proper "startmapaddress" changes from machine to machine and version of ROOT.
from bin/GSSort_ 0x0804f770 in from bin/GSSort_ 0x0804c381 in from bin/GSSort_ 0x01053e33 in __libc_start_main + 0xe3 from /lib/tls/libc.so.6 0x080490a9 in __gxx_personality_v0 + 0x71 from bin/GSSort_
 sometimes this is seen when GSSort is compiled with the optimizer on.
In the Makefile.`uname`.`uname -r`, remove "-O" and recompile. This
might be a bug in GSSort, but it is hard to find since the error goes
away when GSSort is compiled with -g in order
to find the bug in the first place. It could also
just be a bug in the optimize. Either of the problems will hopefully
go away in the future.