From: Immanuel Scheerer <scheerei@in.tum.de>
To: rhug-rhats@sources.redhat.com
Subject: Re: rhug/rhino from 2005-01-11 build failure with jar -c@
Date: Wed, 12 Jan 2005 09:18:00 -0000 [thread overview]
Message-ID: <41E4EB6F.8080307@in.tum.de> (raw)
In-Reply-To: <20050111201103.GA28892@sauna.l.org>
Timo Juhani Lindfors wrote:
> (cd upstream/toolsrc && \
> (../../listclasses rhino-tools; \
> for i in upstream/toolsrc/org/mozilla/javascript/tools/resources/Messages.properties; do echo $i; done | \
> sed -e 's:^upstream/toolsrc/::') | \
> jar -c@) > rhino-tools-1.5R3.jar
> Illegal option: @
> Usage: jar {ctxu}[vfm0Mi] [jar-file] [manifest-file] [-C dir] files ...
I think you are using the jar-binary shipped with the SUN SDK. libgcj itself
provides a jar binary with following usage:
Usage: jar {ctxuV}[vfm0ME@] [jar-file] [manifest-file] [-C dir] files ...
The option -@ (read names from stdin) is not provided by the jar-binary from SUN.
I suppose the problem can be solved by changing $PATH so that the path with the
libgcj-binaries comes before the path with the SUN-binaries.
I hope this helps you.
Greetings,
Immanuel
next prev parent reply other threads:[~2005-01-12 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 20:11 Timo Juhani Lindfors
2005-01-12 9:18 ` Immanuel Scheerer [this message]
2005-01-13 5:24 ` Timo Juhani Lindfors
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=41E4EB6F.8080307@in.tum.de \
--to=scheerei@in.tum.de \
--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).