From: Anthony Green <green@redhat.com>
To: tromey@redhat.com
Cc: rhug-rhats@sources.redhat.com
Subject: [Fwd: Too many args during make dist...]
Date: Sun, 03 Mar 2002 10:41:00 -0000 [thread overview]
Message-ID: <1015180898.1926.109.camel@dhcppc2> (raw)
[-- Attachment #1: Type: text/plain, Size: 31 bytes --]
Oops - wrong email address...
[-- Attachment #2: Forwarded message - Too many args during make dist... --]
[-- Type: message/rfc822, Size: 603 bytes --]
From: Anthony Green <green@redhat.com>
To: tromey@redhat.com
Cc: rhug-rhats@redhat.com
Subject: Too many args during make dist...
Date: 03 Mar 2002 10:39:33 -0800
Message-ID: <1015180776.1926.107.camel@dhcppc2>
Hey Tom,
I've had to strip the doc files out of the xalan tarball because "make
dist" can't handle the number of files (~2800) in this package. The
shell is complaining about too many arguments on the command line. Is
there a common work-around?
AG
next reply other threads:[~2002-03-03 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 10:41 Anthony Green [this message]
2002-03-04 12:56 ` Tom Tromey
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=1015180898.1926.109.camel@dhcppc2 \
--to=green@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
--cc=tromey@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).