public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andy.riebs at hpe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/96302] New: Linux build of gnat/ada fails for lack of gnatdll
Date: Thu, 23 Jul 2020 17:54:45 +0000	[thread overview]
Message-ID: <bug-96302-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96302

            Bug ID: 96302
           Summary: Linux build of gnat/ada fails for lack of gnatdll
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
          Assignee: unassigned at gcc dot gnu.org
          Reporter: andy.riebs at hpe dot com
  Target Milestone: ---

In a build with gnat on a Linux system (CentOS 7.x on amd64/x86_64, in my
case), the attempt to install gnatdll results in an error.

For non-Windows users, my work-around for this is

--- gcc/ada/gcc-interface/Make-lang.in.orig     2020-07-22 15:52:11.939013857
-0400
+++ gcc/ada/gcc-interface/Make-lang.in  2020-07-22 15:53:12.665368912 -0400
@@ -838,8 +838,8 @@
              $(INSTALL_PROGRAM) $$tool$(exeext)
$(DESTDIR)$(bindir)/$$install_name; \
            fi ; \
          done; \
-         $(RM) $(DESTDIR)$(bindir)/gnatdll$(exeext); \
-         $(INSTALL_PROGRAM) gnatdll$(exeext)
$(DESTDIR)$(bindir)/gnatdll$(exeext); \
+#        $(RM) $(DESTDIR)$(bindir)/gnatdll$(exeext); \
+#        $(INSTALL_PROGRAM) gnatdll$(exeext)
$(DESTDIR)$(bindir)/gnatdll$(exeext); \
        fi

             reply	other threads:[~2020-07-23 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 17:54 andy.riebs at hpe dot com [this message]
2020-07-24  7:05 ` [Bug ada/96302] " charlet at gcc dot gnu.org

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=bug-96302-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).