public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/64492] New: Disabling libada prevents building gnattools-cross
Date: Sun, 04 Jan 2015 22:30:00 -0000	[thread overview]
Message-ID: <bug-64492-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64492
           Summary: Disabling libada prevents building gnattools-cross
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
          Assignee: unassigned at gcc dot gnu.org
          Reporter: simon at pushface dot org

Created attachment 34375
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34375&action=edit
Patch to add --enable-cross-gnattools

This is related to PR19959.

--disable-libada is necessary for targets (such as arm-eabi) where the RTS
isn’t distributed as part of GCC. Of course, you still need the cross gnattools
(such as arm-eabi-gnatls).

Unfortunately you can’t build the cross gnattools, because --disable-libada
adds gnattools to the list  of unconfigured directories, which means that the
directory gcc/ada/tools is never created, let alone populated.
gcc/ada/gcc-interface/Makefile.in touches stamp-tools, but that’s all.

You can’t say "make -C gcc gnattools-cross", because that’s in gnattools/. You
can’t say “make -C gcc cross-gnattools”, because the gcc/ada/tools directory
doesn’t exist.

Why does gcc/ada/gcc-interface/Makefile.in touch ../stamp-tools?
Where does the target cross-gnattools come into the picture?

I attach a patch to the top-level configure.ac which adds a new switch
--enable-cross-gnattools.

If you configure with --disable-libada, gnattools is removed from the list of
configured directories unless
* you give --enable-cross-gnattools
* and you are building a cross compiler
* and the target vendor is “none” or “unknown”.

With this patch, the normal configure/make runs through and builds the cross
gnattools without further ado. Tested on 4.9.1, --target=arm-eabi. The patch
applies to the gcc-5-20141228 snapshot with a 17-line offset.
>From gcc-bugs-return-472191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 04 22:49:40 2015
Return-Path: <gcc-bugs-return-472191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13795 invoked by alias); 4 Jan 2015 22:49:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13768 invoked by uid 48); 4 Jan 2015 22:49:31 -0000
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/64492] Disabling libada prevents building gnattools-cross
Date: Sun, 04 Jan 2015 22:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simon at pushface dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget cf_gcchost cf_gccbuild
Message-ID: <bug-64492-4-EzYzcXhkpB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64492-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64492-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg00185.txt.bz2
Content-length: 648

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd492

simon at pushface dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |arm-eabi
               Host|                            |x86_64-apple-darwin13
              Build|                            |x86_64-apple-darwin13

--- Comment #1 from simon at pushface dot org ---
Notes:

The patch was originated by Luke A. Guest.

I have built GCC 5 snapshot 20141228 as host and cross with this patch and used
the result to build an Ada RTS for STM32F4.


             reply	other threads:[~2015-01-04 22:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 22:30 simon at pushface dot org [this message]
2015-01-05  8:20 ` [Bug ada/64492] " ebotcazou at gcc dot gnu.org
2015-01-05  8:33 ` ebotcazou at gcc dot gnu.org
2015-01-05  8:52 ` simon at pushface dot org
2015-01-05  8:55 ` charlet at adacore dot com
2015-01-05  8:55 ` simon at pushface dot org
2015-01-05 10:17 ` ebotcazou at gcc dot gnu.org
2015-01-05 10:18 ` ebotcazou at gcc dot gnu.org
2015-01-05 10:22 ` ebotcazou at gcc dot gnu.org
2015-01-05 11:15 ` laguest at archeia dot com
2015-01-05 14:01 ` simon at pushface dot org
2015-01-05 14:26 ` simon at pushface dot org
2015-01-05 17:57 ` laguest at archeia dot com

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-64492-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).