bug-mes
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jan Nieuwenhuizen
Subject: Re: [bug-mes] mes target selection - currently hardcoded
Date: Mon, 04 Feb 2019 20:36:04 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Danny Milosavljevic writes:

>> if [ -z $build_system ]
>> then
>>   build_system=`uname -m` # if we want it
>
> Or
>
> $ gcc -dumpmachine
> x86_64-unknown-linux-gnu
> $ guix environment -s armhf-linux --pure --ad-hoc binutils coreutils guile 
> gcc-toolchain
> [env]$ gcc -dumpmachine
> arm-unknown-linux-gnueabihf

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 and it has

    (host-type (option-ref options 'host %host-type))

It does not handle cross build correctly, though.

There's also a configure.sh that's used during Guix bootstrap.  It
currently does this

--8<---------------cut here---------------start------------->8---
host=${host-$($CC -dumpmachine 2>/dev/null || echo x86)}
if [ -z "$host" ]; then
    arch=${arch-$(get_machine || uname -m)}
else
--8<---------------cut here---------------end--------------->8---

get_machine comes from mescc-tools...Too many options?

janneke

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com



reply via email to

[Prev in Thread] Current Thread [Next in Thread]