public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC depending on perl?
Date: Thu, 27 Sep 2001 10:57:00 -0000	[thread overview]
Message-ID: <or66a4y0sc.fsf@localhost.localdomain> (raw)
In-Reply-To: <3BB347B0.3080100@cygnus.com>

On Sep 27, 2001, Andrew Cagney <ac131313@cygnus.com> wrote:

> (I know about the pre-built manpages)

> A user of a distribution gets different behavour and different results
> depending on if and which perl they have installed.

No.  If they get a release tarball, perl won't be used at all, because
the man-pages will have already been built, and their timestamps will
be correct.  The problem is when you get a CVS tarball.  You're
supposed to have a ``building environment'' for this to work, which
includes bison, autoconf, automake, perl and perhaps other tools I
forget now.  These are not necessary for releases, though.

> A distribution's build behavour should be far more robust than that.

It is more robust than that.  But that's the distribution, not the
random CVS snapshot.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

      reply	other threads:[~2001-09-27 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 19:29 Andrew Cagney
2001-09-27  5:39 ` Alexandre Oliva
2001-09-27  8:37   ` Andrew Cagney
2001-09-27 10:57     ` Alexandre Oliva [this message]

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=or66a4y0sc.fsf@localhost.localdomain \
    --to=aoliva@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).