This is the mail archive of the
mailing list for the Cygwin project.
Re: octave-forge dependency?
- From: Chris Taylor <chris at equate dot dyndns dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 07 Dec 2005 14:56:04 +0000
- Subject: Re: octave-forge dependency?
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
James R. Phillips wrote:
Charles Wilson wrote:
But apparently I can't use octave.
Hm, actually we wouldn't want to lose such a knowledgeable user. We need users
like you in order to improve octave.
Would this work for you? Prior to putting miktex at the front of your path,
say in your .profile, it should be possible to save the unmodified path in an
environmental variable, say PATH_FOR_OCTAVE.
Then write a short shell script named "octave" to start octave, and put it in
/usr/local/bin; something like
When typing "octave" from the command line, the shell script should be found in
the path prior to the octave binary in /usr/bin. octave/octave-forge should
then use the cygwin-native tetex binaries. I don't see any reason why this
Hope you don't give up on octave.
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..
Spinning complacently in the darkness, covered and blinded by a blanket
of little lives, false security has lulled the madness of this world
into a slumber. Wake up! An eye is upon you, staring straight down and
keenly through, seeing all that you are and everything that you will
never be. Yes, an eye is upon you, an eye ready to blink. So face
forward, with arms wide open and mind reeling. Your future has
arrived... Are you ready to go?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html