There's another option : build natively with distcc pointing to
cross-compilers on x86 boxes. All the configuration etc happens natively
and the compiles themselves are sped up. I wonder if that's the approach
Vladimír Čunát took earlier? He made the notes on how to set up distcc for
raspberry pi
Yes, I have done this method in the past as well, but like you say, it only
helps with C and C++. I'd rather have a set up which works for everything
first, and then selectively try and optimise pieces of it (like using
distcc). Although I was wondering how this would play with Nix and getting
On 09/02/2015 15:57, James Haigh wrote:
On 09/02/15 14:16, Harald van Dijk wrote:
On 09/02/2015 14:55, James Haigh wrote:
On 28/01/15 07:42, Luke Clifton wrote:
Hi Bjørn,
I have read that thread. I agree with you 100% that native builds
(on real or virtual hardware) is the only way this can
On 10 February 2015 at 03:58, James Haigh james.r.ha...@gmail.com wrote:
Even for bootstrapping, it should still be possible to do without package
support for cross-compilation. Compiling entirely within Qemu is one,
perhaps crude, way of ‘fixing’ the build platform isolation problem in
On 28/01/15 07:42, Luke Clifton wrote:
Hi Bjørn,
I have read that thread. I agree with you 100% that native builds (on
real or virtual hardware) is the only way this can work. Upstream
doesn't usually care if their software can cross compile, and they
can't maintain it themselves even if
On 09/02/2015 14:55, James Haigh wrote:
On 28/01/15 07:42, Luke Clifton wrote:
Hi Bjørn,
I have read that thread. I agree with you 100% that native builds (on
real or virtual hardware) is the only way this can work. Upstream
doesn't usually care if their software can cross compile, and they
On 03/02/15 13:59, Lluís Batlle i Rossell wrote:
On Mon, Feb 02, 2015 at 04:16:07PM +0100, Bjørn Forsman wrote:
On 2 February 2015 at 01:17, Lluís Batlle i Rossell vi...@viric.name wrote:
I have the bootstrap-tools for armv5tel, they build and the test passes.
On 09/02/15 16:01, Harald van Dijk wrote:
On 09/02/2015 15:57, James Haigh wrote:
[...]
But what I'm saying is that if the package succeeds in compiling
natively but fails to cross-compile, then this is an issue with the
compiler/toolchain. Yes it can be solved by writing configure scripts
On 09/02/15 14:16, Harald van Dijk wrote:
On 09/02/2015 14:55, James Haigh wrote:
On 28/01/15 07:42, Luke Clifton wrote:
Hi Bjørn,
I have read that thread. I agree with you 100% that native builds
(on real or virtual hardware) is the only way this can work.
Upstream doesn't usually care if
On Mon, Feb 02, 2015 at 04:16:07PM +0100, Bjørn Forsman wrote:
On 2 February 2015 at 01:17, Lluís Batlle i Rossell vi...@viric.name wrote:
I have the bootstrap-tools for armv5tel, they build and the test passes.
https://github.com/viric/nixpkgs/tree/make_arm_bootstraptools
Now I try to
On 2 February 2015 at 01:17, Lluís Batlle i Rossell vi...@viric.name wrote:
I have the bootstrap-tools for armv5tel, they build and the test passes.
https://github.com/viric/nixpkgs/tree/make_arm_bootstraptools
Now I try to go further building release-14.12 stdenv.
Cool! I will have a look
I have the bootstrap-tools for armv5tel, they build and the test passes.
https://github.com/viric/nixpkgs/tree/make_arm_bootstraptools
Now I try to go further building release-14.12 stdenv.
On Fri, Jan 30, 2015 at 04:19:49PM +0100, Lluís Batlle i Rossell wrote:
I have the busybox.. but that's
Hi,
Well, I'm on the first leg of my train journey to Brussels. I've
managed to pack these devices: BeagleBone Black; PandaBoard ES;
Raspberry Pi; Chromebook; Archos tablet; Optimus 3D; as well as an
Arduino Duemilanova and some other electronics (and a whole bunch of
power adaptors!). I don't
I have the busybox.. but that's not enough.
Eelco updated the bootstrap tools in the 29th of October, but I cannot find why.
The new bootstrap tools include different binaries.
Eelco updated the stdenv scripts to accomodate the new tools, but without
updating arm or mips tools, hence breaking
On 28/01/15 01:49, Luke Clifton wrote:
[...]
My problem has always been lack of RAM in my ARM devices. I work
mostly with embedded Linux platforms where RAM is 256MB. To provide
perspective, my Laptop (core i7) with 2GB of RAM fails to build some
nixpkgs packages. Small CPU just means longer
Hello all,
I'll try the next days whether I can update the pieces. I'm using native
armv5tel, not cross builds, as usual in nixos-on-arm.
1) Build a static busybox that works for the purpose.
2) Build release-14.12 or master
3) Commit the busybox to the bootstrap svn repository (if I am correct)
On 29 January 2015 at 22:42, Lluís Batlle i Rossell vi...@viric.name wrote:
Hello all,
I'll try the next days whether I can update the pieces. I'm using native
armv5tel, not cross builds, as usual in nixos-on-arm.
Great!
1) Build a static busybox that works for the purpose.
2) Build
On 29 January 2015 at 23:03, Lluís Batlle i Rossell vi...@viric.name wrote:
On Thu, Jan 29, 2015 at 10:58:41PM +0100, Bjørn Forsman wrote:
On 29 January 2015 at 22:42, Lluís Batlle i Rossell vi...@viric.name wrote:
1) Build a static busybox that works for the purpose.
2) Build release-14.12
On 28 January 2015 at 08:42, Luke Clifton ltclif...@gmail.com wrote:
[...]
I once used to think that full system cross compilation was the only way you
should do things (I was an idealist). But it is a dead end. Unless you have
thousands of hours to throw at the problem, it won't work.
Me too.
Hi,
I forgot to say, that was my first email to the list. So hi
everyone! I was told about NixOS by Doaitse Swierstra at Summer School
Utrecht 2013 on the Applied Functional Programming course. I went to
FOSDEM for the first time last year, seeing Domen's excellent talk, and
I've been in
Hi James,
I too am interested in getting NixOS running on ARM, but unfortunately I am
currently unable to dedicate time to the project.
My problem has always been lack of RAM in my ARM devices. I work mostly
with embedded Linux platforms where RAM is 256MB. To provide perspective,
my Laptop
Hi Bjørn,
I have read that thread. I agree with you 100% that native builds (on real
or virtual hardware) is the only way this can work. Upstream doesn't
usually care if their software can cross compile, and they can't maintain
it themselves even if they did. Sometimes it isn't even an option,
On 28 January 2015 at 02:49, Luke Clifton ltclif...@gmail.com wrote:
...
My plan, should I ever get the time, is to set up a virtual machine, try and
bootstrap NixOS for ARM in that, set up hydra, build nixpkgs and then serve
the results to my embedded platforms. I also have dreams of creating
23 matches
Mail list logo
