[Hamlib-cvs-digest] CVS: hamlib README.betatester,1.2,1.3

[Stephane F. <fi...@us...>]

Update of /cvsroot/hamlib/hamlib
In directory usw-pr-cvs1:/tmp/cvs-serv5311

Modified Files:
	README.betatester 
Log Message:
mention to run autogen.sh after checkout

Index: README.betatester
===================================================================
RCS file: /cvsroot/hamlib/hamlib/README.betatester,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** README.betatester	28 May 2002 21:39:13 -0000	1.2
--- README.betatester	22 Sep 2002 11:39:39 -0000	1.3
***************
*** 85,88 ****
--- 85,90 ----
  to do the following commands
  
+ 	chmod +x autogen.sh
+ 	./autogen.sh
  	./configure --config-cache --disable-static --prefix=/some/where
  	make
***************
*** 92,95 ****
--- 94,99 ----
  compilation if you don't plan to use static libraries.
  
+ NOTE: autogen.sh has only to be run the first time after a fresh checkout.
+ 
  * testing Hamlib
  
***************
*** 111,117 ****
  
  Let's say you own an Icom IC-756:
! 	rigctl -vvvv -r /dev/ttyS0 -m 326
  
! The -vvvv is very important since this will increase verbosity, and give
  precious traces to developpers if something goes wrong. At this level, 
  the protocol data exchanged will also be dumped.
--- 115,121 ----
  
  Let's say you own an Icom IC-756:
! 	rigctl -vvvvv -r /dev/ttyS0 -m 326
  
! The -vvvvv is very important since this will increase verbosity, and give
  precious traces to developpers if something goes wrong. At this level, 
  the protocol data exchanged will also be dumped.
***************
*** 149,153 ****
  	$ script my_rig_traces.txt
  	Script started, file is my_rig_traces.txt
! 	$ rigctl -vvvv -r /dev/ttyS0 -m 326
  	rig:rig_init called
  	rig: loading backend icom
--- 153,157 ----
  	$ script my_rig_traces.txt
  	Script started, file is my_rig_traces.txt
! 	$ rigctl -vvvvv -r /dev/ttyS0 -m 326
  	rig:rig_init called
  	rig: loading backend icom