From: Jakub Jelinek <jakub@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix install-plugin on arm and aarch64
Date: Wed, 06 Mar 2013 11:06:00 -0000 [thread overview]
Message-ID: <20130306110604.GR12913@tucnak.redhat.com> (raw)
In-Reply-To: <513720FF.9010102@ubuntu.com>
On Wed, Mar 06, 2013 at 06:57:03PM +0800, Matthias Klose wrote:
> Am 06.03.2013 17:07, schrieb Jakub Jelinek:
> > https://bugzilla.redhat.com/show_bug.cgi?id=910926
> > reports that plugins aren't usable on arm, because arm-cores.def isn't
> > installed into the plugins directory. arm-cores.def can't be included in
> > tm_file list, because we don't want to include it directly, nor in
> > HeaderInclude in arm.opt (that breaks the build). rs6000 has similar issue
> > with its rs6000-builtin.def, and solves this by adding content to TM_H
> > in Makefile fragment.
> >
> > Thus, the following patch does the same for arm (and apparently aarch64 has
> > the same issue). Ok for trunk?
>
> There is still vxworks-dummy.h, which is not installed, see PR45078. Would the
> same approach work?
i386/x86_64 solves that by tm_file="vxworks-dummy.h ${tm_file}" in
config.gcc. Perhaps arm, mips, sh and sparc should follow that.
Jakub
next prev parent reply other threads:[~2013-03-06 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 9:07 Jakub Jelinek
2013-03-06 9:32 ` Marcus Shawcroft
2013-03-06 10:57 ` Matthias Klose
2013-03-06 11:06 ` Jakub Jelinek [this message]
2013-03-06 12:44 ` [PATCH] Fix install-plugin with vxworks-dummy.h (PR plugins/45078) Jakub Jelinek
2013-03-08 17:24 ` Jakub Jelinek
2013-03-12 15:47 ` Matthias Klose
2013-03-06 23:05 ` [PATCH] Fix install-plugin on arm and aarch64 Ramana Radhakrishnan
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=20130306110604.GR12913@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@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).