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/
