Gnus development mailing list
 help / color / mirror / Atom feed
From: Henrik Enberg <henrik@enberg.org>
Subject: Re: configure hangs with latest cvs
Date: Thu, 27 Sep 2001 22:12:39 +0200	[thread overview]
Message-ID: <m366a4jsug.fsf@enberg.org> (raw)
In-Reply-To: <2nk7ykjymd.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Thu, 27 Sep 2001 14:07:54 -0400")

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> 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. 

It might also be a good idea to change the wording to non-free or
proprietary instead of commercial.

>From <URL:http://www.gnu.org/philosophy/words-to-avoid.html>

Please don't use ``commercial'' as a synonym for ``non-free''. That
confuses two entirely different issues.

A program is commercial if it is developed as a business activity. A
commercial program can be free or non-free, depending on its
license. Likewise, a program developed by a school or an individual can
be free or non-free, depending on its license. The two questions, what
sort of entity developed the program and what freedom its users have,
are independent.

Henrik
-- 
Look!  A ladder!  Maybe it leads to heaven, or a sandwich!




  parent reply	other threads:[~2001-09-27 20:12 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
2001-09-27 18:22   ` Emerick Rogul
2001-09-27 20:12   ` Henrik Enberg [this message]
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=m366a4jsug.fsf@enberg.org \
    --to=henrik@enberg.org \
    /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).