From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: ebotcazou@adacore.com
Subject: [PATCH] Fix PR864, apply program_transform_name to ada tools
Date: Mon, 07 Jan 2013 09:49:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1301071045080.6889@zhemvz.fhfr.qr> (raw)
This makes us unconditionally apply program_transform_name when installing
$(ADA_TOOLS). It's a patch distros have been applying for ages (now
I've updated it for 4.8 which meant re-writing it completely so I am
eligible to submit it).
Bootstrapped on x86_64-unknown-linux-gnu with --program-suffix=-4.8,
installed (and installation inspected) and tested (which uses the
unsuffixed names - names get changed at install time only).
Ok for trunk?
Thanks,
Richard.
2013-01-04 Richard Biener <rguenther@suse.de>
PR ada/864
* gcc-interface/Make-lang.in (ada.install-common): Always apply
program_transform_name.
Index: gcc/ada/gcc-interface/Make-lang.in
===================================================================
--- gcc/ada/gcc-interface/Make-lang.in (revision 194900)
+++ gcc/ada/gcc-interface/Make-lang.in (working copy)
@@ -736,14 +736,13 @@ ada.install-common:
-if [ -f gnat1$(exeext) ] ; \
then \
for tool in $(ADA_TOOLS) ; do \
+ install_name=`echo $$tool|sed '$(program_transform_name)'`$(exeext); \
+ $(RM) $(DESTDIR)$(bindir)/$$install_name; \
if [ -f $$tool-cross$(exeext) ] ; \
then \
- install_name=`echo $$tool|sed '$(program_transform_name)'`$(exeext); \
- $(RM) $(DESTDIR)$(bindir)/$$install_name; \
$(INSTALL_PROGRAM) $$tool-cross$(exeext) $(DESTDIR)$(bindir)/$$install_name; \
else \
- $(RM) $(DESTDIR)$(bindir)/$$tool$(exeext); \
- $(INSTALL_PROGRAM) $$tool$(exeext) $(DESTDIR)$(bindir)/$$tool$(exeext); \
+ $(INSTALL_PROGRAM) $$tool$(exeext) $(DESTDIR)$(bindir)/$$install_name; \
fi ; \
done; \
$(RM) $(DESTDIR)$(bindir)/gnatdll$(exeext); \
next reply other threads:[~2013-01-07 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 9:49 Richard Biener [this message]
2013-01-07 9:51 ` Arnaud Charlet
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=alpine.LNX.2.00.1301071045080.6889@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@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).