On Tue, Jun 25, 2013 at 2:38 AM, Stephen J. Turnbull <stephen(a)xemacs.org>wrote:
Jerry James writes:
> That would be 4.12. Versions 4.11 and earlier choke on the new
> texinfo.tex in various ways. What would you all like me to do? Roll
> back the change to texinfo.tex?
no, no, No, NO, NoNoNoNo NO! :-)
I agree with Stephen.
Seriously, 5.1 is already showing up on some of my distros. We will
need 5.x compatibility in the near future, and I don't see any real
point in trying to pick up just enough to make things 5.x compatible.
> Refuse to work with a texinfo older than 4.12?
I want to hear what Robert says, because I think he's a special case.
I suspect most people building XEmacs on Mac OS X have Fink, MacPorts,
or Homebrew installed, and have the relevant bin directory early in
their PATH. So it's a no-op (or a one-time upgrade of Texinfo) for
us, fixing things for Robert is what this is about.
I think the solution
could be to r
equire users such as myself to use an upgraded makeinfo, or refuse to
upgrade the docs that fail to build, but do not stop the exec build or
In fact, as I wrote in my initial post, I figured out the solution before
I posted. I think configure should have figured it out for me. The errors
would not necessarily hit one as a problem with makeinfo version.
My use of placing /usr/bin before /opt/local/bin in my XEmacs build
environment came from a problem a while ago where macports libraries would
be pulled in when I wanted system ones. That may show up on other users' OS
changed the path in my XEmacs build environment to the one I use for
everyday use, the one with /opt/local/bin before /usr/bin, and everything
works automatically, again. But I still think that configure should
complain when it finds it cannot build some part of the installation if
that will cause the build to stop before creating and installable
, for example, if it cannot find a suitable widget set for Xaw3d. Some of
the configuration files I have used will actually search around for tools
(in the path) that are needed to compile the source tree, given the
variants. I have no idea how such magic is accomplished, and I am not sure
it is necessarily the right thing to do automatically.
My inclination is what Mats suggested: if makeinfo is too old,
the doc build.
If we get complaints about that, I can build an .info tarball (and
maybe .elc, and trim the main distribution tarball down to just the
source ma'am, as Mats suggested elsewhere -- I still don't like that,
Robert Royar <xemacs(a)royar.org>
XEmacs-Beta mailing list