Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 22 Apr 2005 00:18:55 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: can not run OPUS MAKE Message-ID: <20050422041855.GA17881@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Wed, Apr 20, 2005 at 11:42:49AM -0600, lin q wrote: >Hi, > It is strange:in cygwin when I am trying to run OPUS MAKE, I always get >this error, > >OPUS MAKE: Don't know how to make '!*'. Stop. > > I turn on the debug mode and I see the following, > > >*** Read c:\opus6.12/make.ini *** > >Note: You are using Opus' default initialization file 'c:\opus6.12/make.ini' > >*** Done c:\opus6.12/make.ini *** >*** Read \s/make.dbg.nt *** >*** Done \s/make.dbg.nt *** >*** Tracing OPUS MAKE *** >??!* absent >?? check rules >?? no inferred source found >?? update !* >OPUS MAKE: Don't know how to make '!*'. Stop. > > >If I run OPUS MAKE against same makefile in tc-shell, then there is no >problem. > >I wonder if there is any known problem? I just downloaded opus make to see if I could duplicate this problem. I can't. Given that '!*' has some meaning to shells, I wonder if you are tripping over some alias or function gone awry. If you specify the full command line to the make executable when you run the command you should bypass any aliases or functions that you have in the make environment. Otherwise, it's possible that there is something else being triggered. Try doing a 'set -x; c:\path\to\make ; set +x' to see what is happening when you invoke make. cgf -- 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/