From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] microblazeel_v2 are 64-bit executables
Date: Thu, 17 May 2012 20:12:22 +0200 [thread overview]
Message-ID: <87ipfupth5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120516192453.7GAXH.715646.imail@fed1rmwml114> (chrisgriffith@cox.net's message of "Wed, 16 May 2012 16:24:53 -0700")
>>>>> <chrisgriffith@cox.net> writes:
Hi,
> Hi everyone, I hope this is a good place for this, I did search the
> archives and the buglist, and I think it's more informational than a
> bug. As background, I'm using buildroot-2012.05-rc1 on Ubuntu 11.10
> inside VirtualBox on Windows 7, targeting a MicroBlaze AXI system
> with MMU on a Xilinx ML605 development board.
> So it's not a dealbreaker to use the external V1 tools and say so in
> the buildroot config, I just thought you might like to know that the
> default downloaded MB toolchain doesn't always work from the get-go
> and maybe put in a warning or something.
Ahh, interesting. Strange that they did a 64bit build. Is there any
functional reason to use the v2 toolchain rather than v1?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-05-17 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 23:24 [Buildroot] microblazeel_v2 are 64-bit executables chrisgriffith at cox.net
2012-05-17 18:12 ` Peter Korsgaard [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=87ipfupth5.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.