public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yselkowitz at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/57795] Fail Canadian cross building Ada Date: Tue, 14 Jan 2014 09:14:00 -0000 [thread overview] Message-ID: <bug-57795-4-TvY5ddY14v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57795-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57795 Yaakov (Cygwin Ports) <yselkowitz at users dot sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yselkowitz at users dot sourceforg | |e.net --- Comment #1 from Yaakov (Cygwin Ports) <yselkowitz at users dot sourceforge.net> --- I also ran into this when cross-compiling a native gcc with Ada (i686-pc-cygwin/x86_64-pc-cygwin/x86_64-pc-cygwin) in the process of porting GNAT to a new platform. In fact, I believe this would happen any time $build != $host (regardless of $target), but NOT with the typical cross-compiler ($build == $host, $host != $target). The root of the problem is RTS_DIR override (immediately prior to gnattools-cross rule) in gnattools/Makefile.in, which calls gnatls (for $build) where IIUC it should be something like $(GNATMAKE:gnatmake=gnatls) (for $host). There is another problem in this situation: in gcc/ada/gcc-interface/Make-lang.in, the xgnatugn rule (part of building doc/projects.texi and doc/gnat_ugn.texi) calls $(GNATMAKE), resulting in a xgnatugn which runs on $host instead of $build; this probably needs to be just gnatmake instead.
next prev parent reply other threads:[~2014-01-14 9:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-03 8:48 [Bug ada/57795] New: Fail " alexpux at gmail dot com 2014-01-14 9:14 ` yselkowitz at users dot sourceforge.net [this message] 2014-01-14 10:35 ` [Bug ada/57795] Fail Canadian " 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-57795-4-TvY5ddY14v@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: linkBe 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).