public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/60411] ADA bootstrap failure on ARM
Date: Mon, 10 Mar 2014 12:48:00 -0000 [thread overview]
Message-ID: <bug-60411-4-Szbepulz2N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60411-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60411
Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
OK,
the cross build for arm-linux-gnueabihf succeeds again.
So I will close this tracker now.
Thanks,
BUT if I look at these lines in gcc/ada/gcc-interace/Makefile.in:
# ARM android
ifeq ($(strip $(filter-out arm% linux-androideabi,$(target_cpu)
$(target_os))),)
LIBGNAT_TARGET_PAIRS = \
a-intnam.ads<a-intnam-linux.ads \
s-inmaop.adb<s-inmaop-posix.adb \
s-intman.adb<s-intman-posix.adb \
s-linux.ads<s-linux.ads \
s-osinte.adb<s-osinte-android.adb \
s-osinte.ads<s-osinte-android.ads \
s-osprim.adb<s-osprim-posix.adb \
s-taprop.adb<s-taprop-posix.adb \
s-taspri.ads<s-taspri-posix-noaltstack.ads \
s-tpopsp.adb<s-tpopsp-posix-foreign.adb \
system.ads<system-linux-armel.ads \
$(DUMMY_SOCKETS_TARGET_PAIRS)
TOOLS_TARGET_PAIRS = \
mlib-tgt-specific.adb<mlib-tgt-specific-linux.adb \
indepsw.adb<indepsw-gnu.adb
GNATRTL_SOCKETS_OBJS =
EXTRA_GNATRTL_TASKING_OBJS=s-linux.o
EH_MECHANISM=
THREADSLIB =
GNATLIB_SHARED = gnatlib-shared-dual
LIBRARY_VERSION := $(LIB_VERSION)
endif
So they use the same system.ads, which now links with a-exexpr-gcc.adb;
Should'nt this target now also use EH_MECHANISM=-gcc or -arm?
next prev parent reply other threads:[~2014-03-10 12:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 13:54 [Bug ada/60411] New: ADA canadian cross build fails bernd.edlinger at hotmail dot de
2014-03-04 17:24 ` [Bug ada/60411] " mikpelinux at gmail dot com
2014-03-06 14:22 ` bernd.edlinger at hotmail dot de
2014-03-07 20:36 ` [Bug ada/60411] ADA bootstrap failure on ARM charlet at gcc dot gnu.org
2014-03-07 20:57 ` bernd.edlinger at hotmail dot de
2014-03-10 12:48 ` bernd.edlinger at hotmail dot de [this message]
2014-03-10 13:26 ` Arnaud Charlet
2014-03-10 13:27 ` charlet at adacore dot com
2014-04-08 8:24 ` ebotcazou at gcc dot gnu.org
2014-04-08 9:04 ` ebotcazou at gcc dot gnu.org
2014-04-08 20:35 ` ebotcazou at gcc dot gnu.org
2014-04-08 21:27 ` gnugcc at marino dot st
2014-04-08 21:49 ` gnugcc at marino dot st
2014-04-09 7:58 ` ebotcazou at gcc dot gnu.org
2014-04-09 7:59 ` ebotcazou at gcc dot gnu.org
2014-04-09 8:02 ` [Bug ada/60411] Ada " ebotcazou at gcc dot gnu.org
2014-04-09 9:58 ` gnugcc at marino dot st
2014-04-09 12:46 ` gnugcc at marino dot st
2014-04-09 13:02 ` ebotcazou at gcc dot gnu.org
2014-04-09 13:27 ` gnugcc at marino dot st
2014-04-09 13:48 ` ebotcazou at gcc dot gnu.org
2014-04-10 9:52 ` gnugcc at marino dot st
2014-04-10 10:20 ` ebotcazou at gcc dot gnu.org
2014-04-11 16:28 ` gnugcc at marino dot st
2014-04-17 9:14 ` gnugcc at marino dot st
2014-04-17 10:54 ` ebotcazou 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-60411-4-Szbepulz2N@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).