From: Nathan Froyd <froydnj@codesourcery.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
Michael Eager <eager@eagercon.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] powerpc-eabi board support for Xilinx
Date: Tue, 04 Nov 2008 21:56:00 -0000 [thread overview]
Message-ID: <20081104215530.GE595@codesourcery.com> (raw)
In-Reply-To: <20081104213453.GA30736@hungry-tiger.westford.ibm.com>
On Tue, Nov 04, 2008 at 04:34:53PM -0500, Michael Meissner wrote:
> On Wed, Oct 22, 2008 at 10:58:00AM -0700, Michael Eager wrote:
> > The attached patch does two things: First, it creates a
> > --with-board=<board> option which will set the default
> > target board for a build with --target=powerpc-*-eabi. The
> > user can still override this with a -m<board> option. Second,
> > it creates -mxilinx, which specifies target options for
> > using various Xilinx PowerPC development boards.
>
> I thought most of the ppc board packages had moved away from adding -m<option>,
> and instead were using specs files or shell script wrappers to add the
> particular libraries that were used. This way they could use an off the shelf
> compiler and not have to add libraries. I must admit to not really knowing
> that part of the market these days.
For what it's worth, we use linker scripts (specified by the user, but
by-and-large provided by us; the user is welcome to create
board-specific linker scripts, of course) to handle most of the bits
that the -m<board> options currently handle. (Libraries and linker
scripts bits seem to be all that -m<board> is used for anyway, and
linker scripts can fill in for both.)
-Nathan
next prev parent reply other threads:[~2008-11-04 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 19:38 Michael Eager
2008-11-04 21:35 ` Michael Meissner
2008-11-04 21:56 ` Nathan Froyd [this message]
2008-11-05 17:13 ` Michael Eager
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=20081104215530.GE595@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=eager@eagercon.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
/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).