public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fenix@io.com
To: gcc-gnats@gcc.gnu.org
Subject: other/3862: During the build process, gccbug is installed using $(INSTALL_PROGRAM) instead of $(INSTALL_SCRIPT)
Date: Sat, 28 Jul 2001 15:26:00 -0000	[thread overview]
Message-ID: <20010728222030.1841.qmail@sourceware.cygnus.com> (raw)

>Number:         3862
>Category:       other
>Synopsis:       During the build process, gccbug is installed using $(INSTALL_PROGRAM) instead of $(INSTALL_SCRIPT)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 28 15:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     fenix@io.com
>Release:        gcc-3.0
>Organization:
>Environment:
cygwin
>Description:
While building gcc, I tried passing INSTALL_PROGRAM_ARGS="-s" to make in order to strip executables when they are installed.  The gccbug shell script is not an executable, but it adds the -s option anyway so strip fails with an "unknown format" error.  It should not be trying to strip a shell script.  It tries because the line to install gccbug uses the $(INSTALL_PROGRAM) variable instead of the $(INSTALL_SCRIPT) variable.
>How-To-Repeat:
after configuring gcc and making all, use make install INSTALL_PROGRAM_ARGS="-s" and it should fail when trying to install gccbug
>Fix:
I have attached a patch which I believe fixes the problem.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-28 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-28 15:26 fenix [this message]
2001-07-28 20:05 aoliva
2001-11-14 10:16 neil
2001-11-14 10:26 neil

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=20010728222030.1841.qmail@sourceware.cygnus.com \
    --to=fenix@io.com \
    --cc=gcc-gnats@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).