Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: configure hangs with latest cvs
Date: Thu, 27 Sep 2001 14:07:54 -0400	[thread overview]
Message-ID: <2nk7ykjymd.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <vuovgi4ee52.fsf@csa.bu.edu> (Emerick Rogul's message of "Thu, 27 Sep 2001 13:29:13 -0400")

Emerick Rogul <emerick@cs.bu.edu> writes:

> Hi,
>
> When I pull the latest version of gnus out of cvs and run configure,
> it hangs at the step "checking for commercial fonts..."  Apparently,
> it's waiting for some type of input, because if I hit C-d a few times,
> it continues on its way.  I tried specifying --without-fonts to
> configure, but I still run into the same problem.  It looks like the
> calls to latex in the configure script are requiring some type of
> input...  Does anyone know how to fix this?

Probably it is fixed now. Please try again. 

ShengHuo



  reply	other threads:[~2001-09-27 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 17:29 Emerick Rogul
2001-09-27 18:07 ` ShengHuo ZHU [this message]
2001-09-27 18:22   ` Emerick Rogul
2001-09-27 20:12   ` Henrik Enberg
2001-09-27 21:10     ` ShengHuo ZHU

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=2nk7ykjymd.fsf@piglet.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).