John and I are seeing a strange documentation build failure on OS X.
Can someone on another platform run tools/gendocs.sh from the doc
directory and tell me if you see the following:
20:46:35 ~/source/ledger-devel/doc (master) > ../tools/gendocs.sh
= Making Inf
No, runs fine here.
makeinfo (GNU texinfo) 5.2
texi2pdf (GNU Texinfo 5.2) 5381
On Mon, Apr 14, 2014 at 2:24 PM, Craig Earls wrote:
> John and I are seeing a strange documentation build failure on OS X.
> Can someone on another platform run tools/gendocs.sh from the doc
> directory and tell me
Thanks Johann, what platform?
On Mon, Apr 14, 2014 at 5:40 AM, Johann Klähn wrote:
> No, runs fine here.
>
> makeinfo (GNU texinfo) 5.2
> texi2pdf (GNU Texinfo 5.2) 5381
>
>
> On Mon, Apr 14, 2014 at 2:24 PM, Craig Earls wrote:
>>
>> John and I are seeing a strange documentation build failure on
Ah, my bad. Arch Linux 64bit.
On Apr 14, 2014 3:04 PM, "Craig Earls" wrote:
> Thanks Johann, what platform?
>
> On Mon, Apr 14, 2014 at 5:40 AM, Johann Klähn wrote:
> > No, runs fine here.
> >
> > makeinfo (GNU texinfo) 5.2
> > texi2pdf (GNU Texinfo 5.2) 5381
> >
> >
> > On Mon, Apr 14, 2014 at
Thanks. It is very strange I get the sed errors using that build of texi2pdf it
must be an underlying tool. --
Craig
On Mon, Apr 14, 2014 at 6:06 AM, Johann Klähn wrote:
> Ah, my bad. Arch Linux 64bit.
> On Apr 14, 2014 3:04 PM, "Craig Earls" wrote:
>> Thanks Johann, what platform?
>>
>> On M
Hi,
I've been digging around a bit to figure out what might go wrong.
Texi2pdf calls texi2dvi, which uses some pretty advanced sed stuff
(branches, labels, etc.), and in the version of texinfo that is installed
on Mac by default (4.8) there seem to be some syntax issues with these.
Using a curren
We noticed this a few weeks ago. I don't know what changed but these built
cleanly a few months ago. I think the most recent Xcode update change dthe way
the command line tools wee installed and shadow the verdin in brew or macports.
But essentially you are correct the docs require modern versio
Seeing all the build failures being reported, I suggest setting up a
Continuous build server for *ledger*.
I spent half a day yesterday in setting up one for *abandon*. It works
fine, is freely hosted on OpenShift, and is integrated with GitHub.
If needing any help in that direction, just ask. I
We have been using Travis for the last few months. --
Craig
On Sun, Apr 27, 2014 at 8:13 AM, Harshad RJ wrote:
> Seeing all the build failures being reported, I suggest setting up a
> Continuous build server for *ledger*.
> I spent half a day yesterday in setting up one for *abandon*. It works
