public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/6852] gnatlib fails to build with newlib because it doesn't set up the include path Date: Tue, 15 Mar 2005 16:11:00 -0000 [thread overview] Message-ID: <20050315161105.16860.qmail@sourceware.org> (raw) In-Reply-To: <20020528182601.6852.geoffk@redhat.com> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-03-15 16:11 ------- Subject: Bug 6852 CVSROOT: /cvs/gcc Module name: gcc Changes by: charlet@gcc.gnu.org 2005-03-15 16:10:23 Modified files: gcc/ada : Makefile.in Log message: 2005-03-08 Doug Rupp <rupp@adacore.com> Bernard Banner <banner@adacore.com> Vincent Celier <celier@adacore.com> Arnaud Charlet <charlet@adacore.com> PR ada/6852 This change works fine when gnatlib is built from the gcc directory, but does not work when using the libada Makefile, since GCC_FOR_TARGET is not passed to ada/Makefile.in, so more work is needed by a Makefile/configure expert. * Makefile.in(gnatlib): Use $(GCC_FOR_TARGET) for compiling library. set GMEM_LIB on ia64 linux to add optional support for gnatmem. Setup gnatlink switch -M for x86_64 linux, as it is already setup for Linux x86. (gnatlib-shared-default): Use GNATLIBCFLAGS as well. Run ranlib on libgccprefix.a Define PREFIX_OBJS for Darwin, to build libgccprefix. (ADA_INCLUDE_SRCS): Split Ada packages. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ada/Makefile.in.diff?cvsroot=gcc&r1=1.112&r2=1.113 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6852
next prev parent reply other threads:[~2005-03-15 16:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20020528182601.6852.geoffk@redhat.com> 2003-05-27 6:07 ` dhazeghi@yahoo.com 2003-05-27 14:55 ` pinskia@physics.uc.edu 2003-06-02 3:08 ` dhazeghi@yahoo.com 2003-06-02 16:44 ` geoffk@geoffk.org 2003-06-16 18:55 ` dhazeghi@yahoo.com 2003-07-14 3:52 ` dhazeghi at yahoo dot com 2003-07-19 17:43 ` pinskia at physics dot uc dot edu 2003-10-21 17:04 ` charlet at gcc dot gnu dot org 2005-03-15 16:11 ` cvs-commit at gcc dot gnu dot org [this message] 2005-03-15 16:32 ` charlet at gcc dot gnu dot org 2005-04-29 7:33 ` charlet at gcc dot gnu dot org [not found] <bug-6852-288@http.gcc.gnu.org/bugzilla/> 2005-12-12 11:27 ` charlet at gcc dot gnu dot 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=20050315161105.16860.qmail@sourceware.org \ --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).