Re: [bug-mes] mes target selection - currently hardcoded

[Danny Milosavljevic]

Hi Janneke,

On Mon, 04 Feb 2019 20:36:04 +0100
Jan Nieuwenhuizen <address@hidden> wrote:

> Hehe, yes -- if you haven't seen it we have a pretty interesting
> configure "situation".  I'm not really happy with this...

> 
> ./configure is a Guile script [does uname] and it has
> There's also a configure.sh that's used during Guix bootstrap.  It
> currently does [gcc, default via uname]

I wondered about it.

It depends on where the start of the bootstrap is which source is a
better source of "truth".

in general "gcc -dumpmachine" output includes the ABI and "uname"
output doesn't (or rather, the latter only as much as you need to
syscall).

I wouldn't worry about it too much.  If the user has to audit mes anyway,
he would also have to read README and see that he should specify the
architecture if we said so :P

So the default should not be used often, whatever it is.

The user would have to read assembly of the architecture in order to
audit mes, so he should know what the architecture is :)

pgppkzxftolvP.pgp
Description: OpenPGP digital signature