public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Anthony Green <green@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: [Fwd: Too many args during make dist...]
Date: Mon, 04 Mar 2002 12:56:00 -0000	[thread overview]
Message-ID: <874rjwf2kt.fsf@creche.redhat.com> (raw)
In-Reply-To: Anthony Green's message of "03 Mar 2002 10:41:36 -0800"

>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:

Anthony> I've had to strip the doc files out of the xalan tarball
Anthony> because "make dist" can't handle the number of files (~2800)
Anthony> in this package.  The shell is complaining about too many
Anthony> arguments on the command line.  Is there a common
Anthony> work-around?

I don't know of one :-(.
Unfortunately you are the first person to hit this particular bug.
I agree it is a real problem, but I'm not certain what we can do about
it.

Tom

  reply	other threads:[~2002-03-04 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03 10:41 Anthony Green
2002-03-04 12:56 ` Tom Tromey [this message]
2002-03-04 12:59   ` Alexandre Petit-Bianco

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=874rjwf2kt.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=green@redhat.com \
    --cc=rhug-rhats@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).