This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [buildrobot] microblaze-elf / microblaze-linux
- From: Michael Eager <eager at eagercon dot com>
- To: Jan-Benedict Glaw <jbglaw at lug-owl dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 26 Nov 2013 08:13:12 -0800
- Subject: Re: [buildrobot] microblaze-elf / microblaze-linux
- Authentication-results: sourceware.org; auth=none
- References: <20131126032612 dot GZ30563 at lug-owl dot de> <5294C34A dot 6000503 at eagercon dot com> <20131126160809 dot GS30563 at lug-owl dot de>
On 11/26/13 08:08, Jan-Benedict Glaw wrote:
On Tue, 2013-11-26 07:50:34 -0800, Michael Eager <eager@eagercon.com> wrote:
On 11/25/13 19:26, Jan-Benedict Glaw wrote:
Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718
(I also think that we'd have the little endian version on the target
list at contrib/config-list.mk ...)
[...]
I do not see this error in my build of microblaze-elf.
I notice that there are flags in your compile that do not appear in mine:
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror
See the introduction email: This is (as advised) with an up-to-date
GCC (just a few days old), using --enable-werror-always at configure
time (as done by .../contrib/config-list.mk).
Missed that email.
Thanks for looking into the issue anyways! (...and what do you
think about adding a microblazeel target to the list?)
Sounds OK to me.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077