CVS: beepcore-c configure,1.14,1.15

William Mills <[email protected]> Thu, 18 Sep 2003 10:43:46 -0700
Newsgroups gmane.network.beep.beepcore.c.cvs
Message-ID <[email protected]>
Update of /cvsroot/beepcore-c/beepcore-c
In directory sc8-pr-cvs1:/tmp/cvs-serv17607

Modified Files:
	configure 
Log Message:
FreeBSD port.  This was done for FreeBSD 4.3 and up, but not on a 5.x machine.  You might have to do more for later versions.

This was build with what I suspect is a much more recent version of autoconf.  I believe thsi will be correct, but you may need to run the autoconf locally if you have any problems.


Index: configure
===================================================================
RCS file: /cvsroot/beepcore-c/beepcore-c/configure,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** configure	8 Sep 2002 03:02:31 -0000	1.14
--- configure	18 Sep 2003 17:43:44 -0000	1.15
***************
*** 1,43 ****
  #! /bin/sh
- 
  # Guess values for system-dependent variables and create Makefiles.
! # Generated automatically using autoconf version 2.13 
! # Copyright (C) 1992, 93, 94, 95, 96 Free Software Foundation, Inc.
  #
  # This configure script is free software; the Free Software Foundation
  # gives unlimited permission to copy, distribute and modify it.
  
! # Defaults:
[...5534 lines suppressed...]
! 
! 
! # configure is writing to config.log, and then calls config.status.
! # config.status does its own redirection, appending to config.log.
! # Unfortunately, on DOS this fails, as config.log is still kept open
! # by configure, so config.status won't be able to write to it; its
! # output is simply discarded.  So we exec the FD to /dev/null,
! # effectively closing config.log, so it can be properly (re)opened and
! # appended to by config.status.  When coming back to configure, we
! # need to make the FD available again.
! if test "$no_create" != yes; then
!   ac_cs_success=:
!   exec 5>/dev/null
!   $SHELL $CONFIG_STATUS || ac_cs_success=false
!   exec 5>>config.log
!   # Use ||, not &&, to avoid exiting from the if with $? = 1, which
!   # would make configure fail if this is the last instruction.
!   $ac_cs_success || { (exit 1); exit 1; }
! fi
  



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf