This is the mail archive of the cygwin 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: Fw: bug in texi2dvi, and hack patch


> Date: Tue, 25 Jan 2005 11:55:24 +0100
> From: Stepan Kasal <kasal@ucw.cz>
> Cc: karl@freefriends.org, dave@boost-consulting.com, bug-texinfo@gnu.org,
>         akim@epita.fr, ebb9@byu.net, cygwin@cygwin.com
> 
> > > Another way to fix the problem is to adopt the solution used by autoconf:
> > > make sure that the variable $ac_executable_extensions, which is set in
> > > config.site on some platforms, gets substituted:
> > > 
> > > 	AC_SUBST(ac_executable_extensions)
> > > 
> > > and put the following to texi2dvi.in:
> > > 
> > > 	for dir in $PATH; do
> > > 	  for exec_ext in '' @ac_executable_extensions@; do
> > > 	    if test -f "$dir/$1" && test -x "$dir/$1"; then
> > > 		...
> > 
> > I'm okay with this method, provided that ac_executable_extensions can
> > be computed reliably (you didn't say how).
> 
> AFAIK, ac_executable_extensions is not computed.  It is set in config.site
> which is included by configure at the beginning of its run.

Then, for Texinfo, we probably should set ac_executable_extensions in
djgpp/config.site, since I don't want to rely on the system-wide
config.site to set that (or even to exist) in a typical DJGPP
installation.

If Autoconf has a similar DJGPP-specific directory in its distro, it
could set ac_executable_extensions there and point CONFIG_SITE to that
file.

Thanks for explaining the other method (which should also be okay, I
think).

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