Hi!
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
>
> Hello,
>
>> Jan, could it be that the ‘basename’ and ‘dirname’ implementations in
>> Gash fail this test? It might be that sed is not needed if you get
>> these right.
>
> Ah, yes! I have added some test to Gash and this
>
> base
Ludovic Courtès writes:
Hello,
> Jan, could it be that the ‘basename’ and ‘dirname’ implementations in
> Gash fail this test? It might be that sed is not needed if you get
> these right.
Ah, yes! I have added some test to Gash and this
basename -- /
failed, producing the empty string, wh
Assaf Gordon writes:
Hello Assaf,
> Technically speaking, these kind of dependencies (e.g. needing SED
> to build a package) arise from autotools, not directly from sed's
> build commands.
Ah yes, course. That is a big difference.
>> Here is what I get:
> [...]
>> ERROR: In procedure scm-error
Hello,
Assaf Gordon skribis:
> Digging a bit further, I see this specific sed program originates
> from autoconf, from the M4 code used to implement basename and dirname,
> e.g. here:
> https://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/m4sugar/m4sh.m4#n922
> https://git.savannah.gnu.org/cg
Hello,
On 2018-12-08 6:46 a.m., Jan Nieuwenhuizen wrote:
Now that we have successfully bootstrapped GuixSD without using Gcc,
Binutils, GNU C lib, I am working to remove other binary bootstrap
seeds; such as SED and GZIP.
I have bootstrapped GNU make and Bash and was looking into building
GZIP,
Hi!
Now that we have successfully bootstrapped GuixSD without using Gcc,
Binutils, GNU C lib, I am working to remove other binary bootstrap
seeds; such as SED and GZIP.
I have bootstrapped GNU make and Bash and was looking into building
GZIP, only to find out that it depends on a SED feature that
