git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: Tay Ray Chuan <rctay89@gmail.com>, git@vger.kernel.org
Subject: Re: Building Documentation in Cygwin
Date: Tue, 27 Jan 2009 10:32:22 -0800	[thread overview]
Message-ID: <7vskn4y4zt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <c115fd3c0901271027s61a33273lfe9dd702a66aac6@mail.gmail.com> (Tim Visher's message of "Tue, 27 Jan 2009 13:27:54 -0500")

Tim Visher <tim.visher@gmail.com> writes:

> On Tue, Jan 27, 2009 at 12:44 PM, Tim Visher <tim.visher@gmail.com> wrote:
>
>>> you might also want to try getting the cygwin package docbook-xml42.
>>
>> Sure enough, I didn't have that installed.  Turns out I should've done
>> that part first too, as it appears to have fixed my problem.  Thanks
>> so much!
>
> Well, I take that back.  I built the docs successfully on the machine
> that is connected to the net.  I couldn't build them on the offline
> box.  Currently my solution is to build them on this box and then
> manually move them over to the offline box.  It'd be nice to not have
> to do this though... :\
>
> Anyway, further help is appreciated! :)

The xml toolchain has a tendency to download dtds from the original source
with a way for you (typically your distribution) to tell it to use a
locally installed version.  "Can build online, fail when offline" is a
sign that it is not using the local copy.

  reply	other threads:[~2009-01-27 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 15:41 Building Documentation in Cygwin Tim Visher
2009-01-27 16:32 ` Tay Ray Chuan
2009-01-27 17:44   ` Tim Visher
2009-01-27 18:27     ` Tim Visher
2009-01-27 18:32       ` Junio C Hamano [this message]
2009-01-27 19:27         ` Tim Visher
2009-01-27 20:05           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vskn4y4zt.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=rctay89@gmail.com \
    --cc=tim.visher@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).