> "JJ" == Jerry James writes:
JJ> Somebody out there has been involved with past attempts to build
JJ> xindy. Please, I would like to make progress on this so I can get
JJ> back to building the coq stack's new versions. Which package used
JJ> to contain xindy?
It is/was part of
On Thu, Apr 11, 2019 at 9:04 PM Jerry James wrote:
>
> On Mon, Apr 8, 2019 at 8:57 AM Jerry James wrote:
> > So clisp has been built for all architectures in Rawhide now. I
> > cannot build it for F30 yet, because the version of gcc with the s390x
> > fix has not yet been submitted as an
On Mon, Apr 8, 2019 at 8:57 AM Jerry James wrote:
> So clisp has been built for all architectures in Rawhide now. I
> cannot build it for F30 yet, because the version of gcc with the s390x
> fix has not yet been submitted as an update. Regardless, can somebody
> who knows how to build xindy try
On Tue, Apr 9, 2019 at 11:47 PM Dridi Boukelmoune
wrote:
> No, for that you should bind port zero instead to get a random one in
> a race-free manner (e.g. parallel execution of multiple tests for
> example).
Ah, thanks. I didn't know about the port zero trick. I'll suggest
that to upstream.
On Mon, Apr 8, 2019 at 4:58 PM Jerry James wrote:
>
> On Mon, Apr 1, 2019 at 9:36 PM Jerry James wrote:
> > That was, in fact, an s390x-specific gcc bug, now fixed in Rawhide.
> > Sadly, the clisp build is still failing in Rawhide, with failures in
> > the socket tests:
>
> The failing test
On Mon, Apr 08, 2019 at 08:57:22AM -0600, Jerry James wrote:
> On Mon, Apr 1, 2019 at 9:36 PM Jerry James wrote:
> > That was, in fact, an s390x-specific gcc bug, now fixed in Rawhide.
> > Sadly, the clisp build is still failing in Rawhide, with failures in
> > the socket tests:
>
> The failing
On Mon, Apr 1, 2019 at 9:36 PM Jerry James wrote:
> That was, in fact, an s390x-specific gcc bug, now fixed in Rawhide.
> Sadly, the clisp build is still failing in Rawhide, with failures in
> the socket tests:
The failing test attempts to bind to localhost:9090. Apparently
something on the
On Sun, Mar 17, 2019 at 9:54 PM Jerry James wrote:
> This appears to be caused by the clisp code incorrectly pairing
> register and volatile. Still, I find gcc's behavior surprising, which
> is why I filed https://bugzilla.redhat.com/show_bug.cgi?id=1689769.
> That may very well be closed as
On Fri, Mar 15, 2019 at 12:48 AM Miro Hrončok wrote:
> Well I meant TeX docs with Sphinx.
> But obviously even that could be wrong, that's why I've used the words "think"
> and "much".
Ah, sorry for the misread. No, I think you are correct. Sphinx seems
to be used mostly to build HTML
On Thu, Mar 14, 2019 at 8:49 PM Jerry James wrote:
> The clisp issue with s390x has been on my TODO list for a long time.
> I've been using most of my Fedora time to hunt down bugs that keep
> other packages from building at all. I seem to be reaching the end of
> that, at last, so I'll try to
On 15. 03. 19 3:51, Jerry James wrote:
On Thu, Mar 14, 2019 at 9:48 AM Miro Hrončok wrote:
I don't think that we build much TeX documentation in our packages.
I think you mean that the packages you maintain don't build much TeX
documentation. :-) I tend a LOT of packages that use (La)TeX,
On Thu, Mar 14, 2019 at 9:48 AM Miro Hrončok wrote:
> I don't think that we build much TeX documentation in our packages.
I think you mean that the packages you maintain don't build much TeX
documentation. :-) I tend a LOT of packages that use (La)TeX, either
directly or indirectly. I've got
t limitation to propagate down to potentially anything that
> used sphinx. (xindy is written in LISP and builds with clisp. There's
> a certain irony in that Jerry is also a maintainer of clisp.)
Yes, I am, and nobody ever mentioned xindy problems to me. There were
no bugs filed against clisp,
On Thu, Mar 14, 2019 at 4:13 AM Miro Hrončok wrote:
> There should be a configuration option that disbales xindly. Does the
> documentation build with it?
>
> latex_use_xindy = False # put it in doc/conf.py or similar
I've got to figure out where to put that option. Coq has its own
On 14. 03. 19 16:17, Jason L Tibbitts III wrote:
"MH" == Miro Hrončok writes:
MH> There should be a configuration option that disbales xindly. Does
MH> the documentation build with it?
Since xindy isn't really something that can be relied upon, is it
possible (or reasonable) to do this
our sphinx packages?
Even when it was enabled, it was architecture-limited which would
force that limitation to propagate down to potentially anything that
used sphinx. (xindy is written in LISP and builds with clisp. There's
a certain irony in that Jerry is also a maintainer of clisp.)
I do th
n.ind" "CoqRefMan.idx"'
Latexmk: calling xindy( -L english -C utf8 -M sphinx.xdy -o
"CoqRefMan.ind" "CoqRefMan.idx" )
Can't exec "xindy": No such file or directory at (eval 12) line 14.
The dependency on xindy comes from Sphinx.
Latexmk: calling xindy( -L english -C utf8 -M sphinx.xdy -o
"CoqRefMan.ind" "CoqRefMan.idx" )
Can't exec "xindy": No such file or directory at (eval 12) line 14.
The dependency on xindy comes from Sphinx. Take a look at
%{python3_sitelib}/sphinx/texinputs/
18 matches
Mail list logo
