From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: powerpc64[le]-linux port progress Date: Sun, 23 Feb 2020 10:01:03 +0100 Message-ID: <87mu99he40.fsf@gnu.org> References: <5f6558fb-5aba-770e-1097-2730262876d4@free.fr> <87imjyvm0e.fsf@gnu.org> <13513d35-0775-5364-86d7-56e6f3f80400@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:48700) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5n8N-000897-F4 for guix-devel@gnu.org; Sun, 23 Feb 2020 04:01:08 -0500 In-Reply-To: <13513d35-0775-5364-86d7-56e6f3f80400@free.fr> (dftxbs3e@free.fr's message of "Sun, 23 Feb 2020 02:34:28 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: dftxbs3e Cc: Guix Devel dftxbs3e writes: Hi! > On 2/22/20 1:34 PM, Jan Nieuwenhuizen wrote: >> Have you tried building static gawk standalone and check it for that >> bash? You could do something like >> >> grep -ao '/gnu/store/e*-bash' $(./pre-inst-env guix build -e '(@@ (gn= u packages make-bootstrap) %static-binaries)') >> >> On my x86_64-linux system, I get >> >> /gnu/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bash > Yes! I used the strings utility. I get two references to bash-static in > the store with 'eeeee'. Ah, "good". > Speaking of which, do you know if it's possible > to be spawned into an environment where %static-binaries's gawk package > (and only that one) sources are extracted, patched and configured? So > that I can investigate the inclusion of bash-static comfortably. You can either do something like ./pre-inst-env guix build -e '(@@ (gnu packages bootstrap) %static-bina= ries)' --keep-failed --no-offload and edit the #:builder to return #f, or copy %static-binaries into a %static-gawk where you strip out other stuff. >> For the new Scheme-only bootstrap, I solved a similar problem for >> %bootstrap-mes by replacing the /gnu/store/eee* store-references with >> actual bootstrap file names; see `%bootstrap-mes-rewired' in >> core-updates http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages= /commencement.scm?h=3Dcore-updates#n251 >> > I hear, however that smells like a hack to me, I'd like to avoid > resorting to such unless absolutely necessary. I'm not entirely sure which is better; but we chose this in order not having to touch the bootstrap binary for mes. Also, I don't know "where you are"; when trying to get "it to work", cutting corners initially works for me :-) > How come it's not > possible to find where that bash-static reference is being inserted? Computers are hard? It's probably easy to find when you see it... Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com