X-Spam-Check-By:	sourceware.org
Message-ID:	<20051207153014.36506.qmail@web51505.mail.yahoo.com>
Date:	Wed, 7 Dec 2005 07:30:14 -0800 (PST)
From:	"James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To:	antiskid56-cygwin AT yahoo DOT com
Subject:	Re: octave-forge dependency?
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Chris Taylor wrote:

>This doesn't solve the core problem that configure will pick up the >presence
of cygwin's tetex and expect it - the cygwin tetex install >would need to be
masked entirely in order to use miktex and not >have configure expect tetex..


OK, it seems an elaboration of the idea could though.  The autoconf/automake
environment needs to be like octave, while the rest of the time, you want
miktex in the front of the path.  Wouldn't executing

export PATH=$PATH_FOR_OCTAVE

before starting ./configure work for that purpose?

jrp

--
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/

- Raw text -