On 13/07/14 13:31, Johannes Pfau via D.gnu wrote:
IIRC building gdc/gcc alone requires 12 hours. And you'll need swap
as there's not enough ram ;-)
Hmmm, I'd like to think I could build gdc-for-arm itself on my regular machine
and just copy it over? ;-)
On 13/07/14 12:30, Johannes Pfau via D.gnu wrote:
AFAIK that's not possible with GCC right now. One GCC build always
targets one main architecture.
Is there any reason why you can't use the binaries from
http://gdcproject.org/downloads/ ?
No, none at all. I just thought, since I build GDC fro
Hello all,
Is there a simple/trivial way to ensure that when I build GDC, I build not only
the native target for my machine (x86_64) but also the arm-linux-gnueabi target?
I decided it was time to start pulling out Adam Ruppe's embedded programming
guide, and as a decidedly non-embedded progr
On 08/07/14 17:58, Iain Buclaw via D.gnu wrote:
My stance at the moment is that DFLAGS should be recognised by the
build tool, not the compiler.
I wonder if John's specific concern may be to do with how dmd uses the DFLAGS
environment variable to specify the standard import and library paths.
On 14/06/14 13:41, Iain Buclaw via D.gnu wrote:
If anyone is privileged enough to have gdc with 2.065 already, then
I'd like to suggest trying out dub and building all packages in
http://code.dlang.org using it, using various different compiler
flags, and report back any bugs found (with nice min
On 12/06/14 00:50, Iain Buclaw via D.gnu wrote:
Bleeding edge, see gcc.version which has the snapshot version of gcc
this was last tested and verified against.
However if the last conversation I had with Johannes was of any
indicator, if you hold onto your horses, you may find this backported
to
On 11/06/14 23:54, Iain Buclaw via D.gnu wrote:
It's done, after 2 months brewing in development.
https://github.com/D-Programming-GDC/GDC/pull/76
Oh, awesome. Congratulations and thanks. :-)
Related note -- what are the recommended/required gcc sources to use? Is 4.9.0
adequate or does th
