fgrep fails to find grep during bootstrap

fgrep fails to find grep during bootstrap

[Carlos Sánchez de La Lama]

Hi all,

I am trying to bootstrap for powerpc-linux. I have generated the
tarballs and patched gnu/packages/bootstrap.scm to use them.

However, I get an error during when creating %bootstrap-coreutils&co
package. It specifies "fgrep" as program to test, but fgrep is a shell
script, and altought the shebang is correctly patched, it needs "grep"
binary in the path (which is not at this stage). fgrep does:

exec grep -F "$@"

so this can not work unless grep is available in PATH.

Options would be to patch those scripts to use `dirname $0`/grep, or
just test another program in package-from-tarball (the program testes
used to be "true"). I am doing the latter to go on bootstraping.

BR

Carlos

-- 
-Tiens! Mais vous êtes un homme de coeur! dit sir Francis Cromarty.
-Quelquefois, répondit simplement Phileas Fogg. Quand j'ai le temps.

Jules Verne, "Le Tour du monde en quatre-vingts jours" (1872)

Re: fgrep fails to find grep during bootstrap

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On Tue, Sep 27, 2016 at 03:00:30PM +0200, Carlos Sánchez de La Lama wrote:
> Hi all,
> 
> I am trying to bootstrap for powerpc-linux. I have generated the
> tarballs and patched gnu/packages/bootstrap.scm to use them.
> 
> However, I get an error during when creating %bootstrap-coreutils&co
> package. It specifies "fgrep" as program to test, but fgrep is a shell
> script, and altought the shebang is correctly patched, it needs "grep"
> binary in the path (which is not at this stage). fgrep does:
> 
> exec grep -F "$@"
> 
> so this can not work unless grep is available in PATH.
> 
> Options would be to patch those scripts to use `dirname $0`/grep, or
> just test another program in package-from-tarball (the program testes
> used to be "true"). I am doing the latter to go on bootstraping.
> 
> BR
> 
> Carlos
> 

I thought it was just me! I've been looking at that test error for a
while with my aarch64 machine(s) and trying to figure out what to do
with it.

have you tried it with reverting commit 84cbe39c5a21495647ab6528715c42e4c5b94e83 ?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: fgrep fails to find grep during bootstrap

[Carlos Sánchez de La Lama]

>> It specifies "fgrep" as program to test, but fgrep is a shell script,
>> and altought the shebang is correctly patched, it needs "grep" binary
>> in the path (which is not at this stage).
>
> have you tried it with reverting commit
> 84cbe39c5a21495647ab6528715c42e4c5b94e83 ?

Kind of; I changed program to test to "true" (like it was before the
commit) but I did not remove the shebang patching, which was being
correctly done and did not harm. That allowed me to go on (and hit the
next problem some minutes later ;) )

Anyways, Mark has fixed it already.

BR

Carlos

Re: fgrep fails to find grep during bootstrap

[Mark H Weaver]

csanchezdll@gmail.com (Carlos Sánchez de La Lama) writes:

> Hi all,
>
> I am trying to bootstrap for powerpc-linux. I have generated the
> tarballs and patched gnu/packages/bootstrap.scm to use them.
>
> However, I get an error during when creating %bootstrap-coreutils&co
> package. It specifies "fgrep" as program to test, but fgrep is a shell
> script, and altought the shebang is correctly patched, it needs "grep"
> binary in the path (which is not at this stage). fgrep does:
>
> exec grep -F "$@"
>
> so this can not work unless grep is available in PATH.

I've fixed this problem on the core-updates branch:

http://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=1063d325ea76aa2b00dfcd3d436b16e412103df1

      Mark