[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-mes] mes target selection - currently hardcoded
From: |
Danny Milosavljevic |
Subject: |
Re: [bug-mes] mes target selection - currently hardcoded |
Date: |
Mon, 4 Feb 2019 20:00:54 +0100 |
On Mon, 04 Feb 2019 19:50:50 +0100
Jan Nieuwenhuizen <address@hidden> wrote:
> Danny Milosavljevic writes:
>
> >> guix environment -s armhf-linux --ad-hoc binutils coreutils
> >
> > Aha, the following does work:
> >
> > $ guix environment -s armhf-linux --pure --ad-hoc binutils coreutils guile
> > [env]$ guile
> > scheme@(guile-user)> (uname)
> > $1 = #("Linux" "dayas" "4.20.0-gnu" "#1 SMP 1" "armv7l")
> >
> > Apparently it had just picked up the x86_64 guile before.
>
> Ah good. Does that mean we can use the default for --build and --host
> and propagate them to mescc?
Yes for Guix.
We can always revisit the defaulter later.
We should print it to the console, then others can see what's happening.
With a not-as-good emulation or with a cross compiler, a user of another
distribution would be very confused otherwise.
pgp9j4HjO7CZ7.pgp
Description: OpenPGP digital signature
Re: [bug-mes] mes target selection - currently hardcoded, Danny Milosavljevic, 2019/02/04