From: David Holsgrove <david.holsgrove@xilinx.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>,
"joseph@codesourcery.com" <joseph@codesourcery.com>,
John Williams <jwilliams@xilinx.com>,
Edgar Iglesias <edgari@xilinx.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>, Tom Shui <tshui@xilinx.com>
Subject: RE: [PATCH v2 0/2] Add MicroBlaze Port
Date: Tue, 09 Apr 2013 08:12:00 -0000 [thread overview]
Message-ID: <043755f5-24cf-455f-9a16-b5506038e81d@VA3EHSMHS002.ehs.local> (raw)
In-Reply-To: <20130408224836.A7B182C088@topped-with-meat.com>
> -----Original Message-----
> From: Roland McGrath [mailto:roland@hack.frob.com]
> Sent: Tuesday, 9 April 2013 8:49 am
> To: David Holsgrove
> Cc: libc-ports@sourceware.org; joseph@codesourcery.com; John Williams; Edgar
> Iglesias; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala; Tom Shui
> Subject: Re: [PATCH v2 0/2] Add MicroBlaze Port
>
> > I did find that by making the following change to Makerules to
> > stop reporting unresolved symbols in object files helped, but
> > again, I'm not confident of the wider implications here;
>
> This is a very bad thing to do for multiple reasons.
> We'll have to discuss alternatives that work with -z defs.
>
Thanks Roland, I understand your concerns posted on the separate libc-alpha
thread (http://sourceware.org/ml/libc-alpha/2013-04/msg00227.html) and agree
that a rushed change to core Make is not the answer here.
I'm eager to get the initial MicroBlaze port included in libc-ports, and then
follow other architectures when a solution is developed.
I see that Joseph is on leave until the 16th April, but in the meantime I'd like
to post my updated patch and reply to his review comments in the original post.
thanks,
David
>
> Thanks,
> Roland
prev parent reply other threads:[~2013-04-09 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 14:28 David Holsgrove
2013-04-02 23:19 ` Joseph S. Myers
2013-04-08 22:48 ` Roland McGrath
2013-04-09 8:12 ` David Holsgrove [this message]
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=043755f5-24cf-455f-9a16-b5506038e81d@VA3EHSMHS002.ehs.local \
--to=david.holsgrove@xilinx.com \
--cc=edgari@xilinx.com \
--cc=joseph@codesourcery.com \
--cc=jwilliams@xilinx.com \
--cc=libc-ports@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=roland@hack.frob.com \
--cc=tshui@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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).