This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problems with cygwin ... no aceptable cc found in $PATH


On Fri, 25 Apr 2003, poseso soy yo wrote:

> Hello,
>    I have windows 2000 like a operating system and installed the last
> version of cygwin. I'm trying to install flite in my computer, and when I
> put "./configure" I have this error:
> configure: error: no acceptable cc found in $PATH
>
> Anybody can help me? The next text is a part of the configure file, I think
> that it give me the problems.
>
>
> if test -z "$CC"; then
>   # Extract the first word of "cc", so it can be a program name with args.
> set dummy cc; ac_word=$2
> echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
> echo "configure:679: checking for $ac_word" >&5
> if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
>   echo $ac_n "(cached) $ac_c" 1>&6
> else
>   if test -n "$CC"; then
>   ac_cv_prog_CC="$CC" # Let the user override the test.
> else
>   IFS="${IFS=   }"; ac_save_ifs="$IFS"; IFS=":"
>   ac_prog_rejected=no
>   ac_dummy="$PATH"
>   for ac_dir in $ac_dummy; do
>     test -z "$ac_dir" && ac_dir=.
>     if test -f $ac_dir/$ac_word; then
>       if test "$ac_dir/$ac_word" = "/usr/ucb/cc"; then
>         ac_prog_rejected=yes
>         continue
>       fi
>       ac_cv_prog_CC="cc"
>       break
>     fi
>   done
>   IFS="$ac_save_ifs"
> if test $ac_prog_rejected = yes; then
>   # We found a bogon in the path, so make sure we never use it.
>   set dummy $ac_cv_prog_CC
>   shift
>   if test $# -gt 0; then
>     # We chose a different compiler from the bogus one.
>     # However, it has the same basename, so the bogon will be chosen
>     # first if we set CC to just the basename; use the full file name.
>     shift
>     set dummy "$ac_dir/$ac_word" "$@"
>     shift
>     ac_cv_prog_CC="$@"
>   fi
> fi
> fi
> fi
> CC="$ac_cv_prog_CC"
> if test -n "$CC"; then
>   echo "$ac_t""$CC" 1>&6
> else
>   echo "$ac_t""no" 1>&6
> fi
>
>   if test -z "$CC"; then
>     case "`uname -s`" in
>     *win32* | *WIN32*)
>       # Extract the first word of "cl", so it can be a program name with args.
> set dummy cl; ac_word=$2
> echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
> echo "configure:730: checking for $ac_word" >&5
> if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
>   echo $ac_n "(cached) $ac_c" 1>&6
> else
>   if test -n "$CC"; then
>   ac_cv_prog_CC="$CC" # Let the user override the test.
> else
>   IFS="${IFS=   }"; ac_save_ifs="$IFS"; IFS=":"
>   ac_dummy="$PATH"
>   for ac_dir in $ac_dummy; do
>     test -z "$ac_dir" && ac_dir=.
>     if test -f $ac_dir/$ac_word; then
>       ac_cv_prog_CC="cl"
>       break
>     fi
>   done
>   IFS="$ac_save_ifs"
> fi
> fi
> CC="$ac_cv_prog_CC"
> if test -n "$CC"; then
>   echo "$ac_t""$CC" 1>&6
> else
>   echo "$ac_t""no" 1>&6
> fi
> ;;
>     esac
>   fi
>   test -z "$CC" && { echo "configure: error: no acceptable cc found in \$PATH" 1>&2; exit 1; }
> fi
>
> Thanks very much,

It's a good habit to attach the output of "cygcheck -svr" to queries of
this sort, as indicated in <http://cygwin.com/problems.html>.  My guess
is, it would show that you haven't installed the "gcc" package.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor at watson dot ibm dot com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]