public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/47467] [4.6 Regression] hwint.h:239:3: error: implicit declaration of function 'abs' Date: Wed, 26 Jan 2011 22:12:00 -0000 [thread overview] Message-ID: <bug-47467-4-EozDECkDq9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47467-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47467 --- Comment #8 from Joel Sherrill <joel at gcc dot gnu.org> 2011-01-26 22:01:56 UTC --- (In reply to comment #7) > > Is targext.c really supposed to be part of LIBGNAT_SRCS for the target or is > > this just a host side compiler helper? > > Unfortunately the former. The symbols defined in targext.c are included by > s-os_lib.adb, which is renamed to g-os_lib.adb for the library. > > Does the following patch work? It appears to. My build tree now has these copies of targext.o. I think you can commit this and close this one. $ find b-gccada-mips/ -name targext.o b-gccada-mips/gcc/ada/rts_mips32_soft-float/targext.o b-gccada-mips/gcc/ada/rts_mips3_el_soft-float/targext.o b-gccada-mips/gcc/ada/targext.o b-gccada-mips/gcc/ada/tools/targext.o > Index: targext.c > =================================================================== > --- targext.c (revision 169285) > +++ targext.c (working copy) > @@ -33,8 +33,13 @@ > /* extension for object and executable files. It is used by the compiler, */ > /* binder and tools. */ > > +#ifdef IN_RTS > +#include "tconfig.h" > +#include "tsystem.h" > +#else > #include "config.h" > #include "system.h" > +#endif > #include "coretypes.h" > #include "tm.h"
next prev parent reply other threads:[~2011-01-26 22:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-26 4:47 [Bug other/47467] New: " danglin at gcc dot gnu.org 2011-01-26 11:39 ` [Bug other/47467] " rguenth at gcc dot gnu.org 2011-01-26 12:39 ` rguenth at gcc dot gnu.org 2011-01-26 12:51 ` rguenth at gcc dot gnu.org 2011-01-26 21:17 ` joel at gcc dot gnu.org 2011-01-26 21:50 ` joel at gcc dot gnu.org 2011-01-26 22:10 ` ebotcazou at gcc dot gnu.org 2011-01-26 22:12 ` joel at gcc dot gnu.org [this message] 2011-01-26 22:41 ` ebotcazou at gcc dot gnu.org 2011-01-26 22:45 ` ebotcazou at gcc dot gnu.org 2011-02-02 18:00 ` dnovillo at gcc dot gnu.org 2011-02-02 18:11 ` dnovillo 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-47467-4-EozDECkDq9@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).