commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jfcl...@apache.org
Subject cvs commit: jakarta-commons/daemon/xdocs faq.xml jsvc.xml
Date Thu, 25 Sep 2003 15:42:12 GMT
jfclere     2003/09/25 08:42:12

  Modified:    daemon/xdocs jsvc.xml
  Added:       daemon/xdocs faq.xml
  Log:
  Start a faq page and add the autoconf version.
  
  Revision  Changes    Path
  1.2       +1 -1      jakarta-commons/daemon/xdocs/jsvc.xml
  
  Index: jsvc.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/daemon/xdocs/jsvc.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jsvc.xml	16 Sep 2003 11:55:08 -0000	1.1
  +++ jsvc.xml	25 Sep 2003 15:42:12 -0000	1.2
  @@ -26,7 +26,7 @@
   <p>
   To build under an UNIX operating system you will need:
   <ul>
  -  <li>GNU AutoConf</li>
  +  <li>GNU AutoConf (at least version 2.53)</li>
     <li>An ANSI-C compliant compiler (GCC is good)</li>
     <li>GNU Make</li>
     <li>A Java Platform 2 compliant SDK</li>
  
  
  
  1.1                  jakarta-commons/daemon/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  <?xml version="1.0"?>
   
  <document>
   
   <properties>
    <title>Daemon : FAQ</title>
    <author email="jfrederic.clere@fujitsu-siemens.con">Jean-Frederic Clere</author>
   </properties>
  
  <body>
  <section name="Buildconf problems">
  <p>
  <source>
  $ sh support/buildconf.sh
  autoconf: Undefined macros:
  ***BUG in Autoconf--please report*** AC_PATH
  ***BUG in Autoconf--please report*** AC_PATH
  ***BUG in Autoconf--please report*** AC_PATH
  </source>
  Your version of autoconf is to old, upgrade your autoconf and retry.
  Or run support/buildconf.sh in another machine and copy the daemon tree in
  the machine where you want to compile jsvc.
  </p>
  </section>
  
  <section name="Configure problems">
  <p>
  <source>
  configure: creating ./config.status
  config.status: creating Makefile
  mv: Makefile: set owner/group (was: 1670/0): Operation not permitted
  config.status: creating Makedefs
  mv: Makedefs: set owner/group (was: 1670/0): Operation not permitted
  config.status: creating native/Makefile
  mv: native/Makefile: set owner/group (was: 1670/0): Operation not permitted
  *** All done ***
  Now you can issue "make"
  </source>
  You should ignore those error messages they are normal in FreeBSD.
  config.status creates files in /tmp and move them in the current directory.
  When FreeBSD creates files it sets the group of the files to
  the group of the directory where the files are created.
  So if /tmp is group "wheel" the files are "wheel". When moving the files in
  the current directory (if you are not member of group "wheel")
  the group "wheel" cannot be set on the moved files.
  </p>
  </section>
  
  </body>
  </document>
  
  
  

Mime
View raw message