public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: java/4295: Install problem for fastjar on Cygwin
Date: Mon, 17 Sep 2001 09:56:00 -0000	[thread overview]
Message-ID: <20010917165600.13944.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR java/4295; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: openup01@rd.francetelecom.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/4295: Install problem for fastjar on Cygwin
Date: 17 Sep 2001 11:02:59 -0600

 >>>>> ">" == openup01  <openup01@rd.francetelecom.com> writes:
 
 >> Synopsis:       Install problem for fastjar on Cygwin
 
 >> After doing the 'make bootstrap' (which works), the 'make install' fails
 >> in directory fastjar with a message like :
 >> chmod : file /usr/bin/#inst.1250# does not exist.
 
 >> It seems that the 'install-binPROGRAMS' target fails to specify correctly
 >> the .exe extension for the install-sh script.
 
 Thanks.  I believe the fix is as easy as adding `AC_EXEEXT' to the
 fastjar configure.in.  However, I don't have easy access to a Cygwin
 box to test this.  If I send you a patch can you test it?  I will send
 a patch that includes the changes to configure and Makefile.in, so you
 won't need autoconf or automake.
 
 Tom


             reply	other threads:[~2001-09-17  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17  9:56 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-17  9:00 tromey
2001-10-17  8:56 Tom Tromey
2001-10-16 20:36 Billinghurst, David (CRTS)
2001-10-16 13:36 Tom Tromey
2001-10-15 19:06 Billinghurst, David (CRTS)
2001-09-17  9:49 tromey
2001-09-11  0:46 openup01

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=20010917165600.13944.qmail@sourceware.cygnus.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).