I'm writing an ebuild that has a src_test() and one of the tests needs
to be a here-document (command <<- EOF). But I need to do a 'die
"Failed"' call if the test fails and I can't get the syntax right.
Imagine this:

src_test() {
./frob <<- EOF || die "frob failed"
foo
bar
EOF
}

It passes 'ebuild digest' but fails on emerge. What's the right syntax?
Here's the error message:

[...]temp/environment: line 2329: syntax error near unexpected token `||'
[...]/temp/environment: line 2329: ` || die "frob failed";'
*
* Call stack:
* ebuild.sh, line 1641: Called die
* The specific snippet of code:
* preprocess_ebuild_env || \
* die "error processing environment"
* The die message:
* error processing environment

Nikos Chantziaras wrote:

> I'm writing an ebuild that has a src_test() and one of the tests needs
> to be a here-document (command <<- EOF). But I need to do a 'die
> "Failed"' call if the test fails and I can't get the syntax right.
> Imagine this:
>
> src_test() {
> ./frob <<- EOF || die "frob failed"
> foo
> bar
> EOF
> }
>
> It passes 'ebuild digest' but fails on emerge. What's the right syntax?

Look:

$ grep aaa <<- EOF || echo "not found"
> bbb
> ccc
> EOF
not found
$ grep aaa <<- EOF || echo "not found"
> bbb
> ccc
> EOF
> EOF
not found

Note that the shell ignores the "EOF" if it has leading whitespace.
My guess is that the closing "EOF" should probably go right at the beginning
of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a similar
construct.

Nikos Chantziaras wrote:

> I'm writing an ebuild that has a src_test() and one of the tests needs
> to be a here-document (command <<- EOF). But I need to do a 'die
> "Failed"' call if the test fails and I can't get the syntax right.
> Imagine this:
>
> src_test() {
> ./frob <<- EOF || die "frob failed"
> foo
> bar
> EOF
> }
>
> It passes 'ebuild digest' but fails on emerge. What's the right syntax?

Look:

$ grep aaa <<- EOF || echo "not found"
> bbb
> ccc
> EOF
not found
$ grep aaa <<- EOF || echo "not found"
> bbb
> ccc
> EOF
> EOF
not found

Note that the shell ignores the "EOF" if it has leading whitespace.
My guess is that the closing "EOF" should probably go right at the beginning
of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a similar
construct.

pk wrote:

> Note that the shell ignores the "EOF" if it has leading whitespace.
> My guess is that the closing "EOF" should probably go right at the
> beginning of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a
> similar construct.

Ok, after some tests it seems that EOF can be indented using tabs, but not
spaces. So, try either putting EOF at the beginning, or indenting it with
tabs only.

pk wrote:

> Note that the shell ignores the "EOF" if it has leading whitespace.
> My guess is that the closing "EOF" should probably go right at the
> beginning of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a
> similar construct.

Ok, after some tests it seems that EOF can be indented using tabs, but not
spaces. So, try either putting EOF at the beginning, or indenting it with
tabs only.

pk wrote:
> pk wrote:
>
>> Note that the shell ignores the "EOF" if it has leading whitespace.
>> My guess is that the closing "EOF" should probably go right at the
>> beginning of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a
>> similar construct.
>
> Ok, after some tests it seems that EOF can be indented using tabs, but not
> spaces. So, try either putting EOF at the beginning, or indenting it with
> tabs only.

It is indented with tabs, and the script runs OK on it's own. It just
won't run inside the portage framework and I don't know why.

pk wrote:
> pk wrote:
>
>> Note that the shell ignores the "EOF" if it has leading whitespace.
>> My guess is that the closing "EOF" should probably go right at the
>> beginning of the line. See eg app-text/htp/htp-1.15.ebuild, which uses a
>> similar construct.
>
> Ok, after some tests it seems that EOF can be indented using tabs, but not
> spaces. So, try either putting EOF at the beginning, or indenting it with
> tabs only.

It is indented with tabs, and the script runs OK on it's own. It just
won't run inside the portage framework and I don't know why.

pk wrote:
> Nikos Chantziaras wrote:
>
>> It is indented with tabs, and the script runs OK on it's own.
>
> How do you run an ebuild on its own? What commands did you try?

With "on its own" I meant that a script using this construct is accepted
perfectly by bash.

#! /bin/sh
../frob <<- EOF || echo "frob failed"
foo
bar
EOF

The above works OK. Btw, when you try to emerge the
app-text/htp-1.15.ebuild you pointed me to (once unmasked), you'll see
that it dies during the early steps with the same message:


/var/tmp/portage/app-text/htp-1.15/temp/environment: line 184: syntax
error near unexpected token `||'
/var/tmp/portage/app-text/htp-1.15/temp/environment: line 184: ` || die'


I guess the only solution is to check the result of the test afterwards
with something like [ $? -eq 0 ] || die "frob failed"

pk wrote:
> Nikos Chantziaras wrote:
>
>> It is indented with tabs, and the script runs OK on it's own.
>
> How do you run an ebuild on its own? What commands did you try?

With "on its own" I meant that a script using this construct is accepted
perfectly by bash.

#! /bin/sh
../frob <<- EOF || echo "frob failed"
foo
bar
EOF

The above works OK. Btw, when you try to emerge the
app-text/htp-1.15.ebuild you pointed me to (once unmasked), you'll see
that it dies during the early steps with the same message:


/var/tmp/portage/app-text/htp-1.15/temp/environment: line 184: syntax
error near unexpected token `||'
/var/tmp/portage/app-text/htp-1.15/temp/environment: line 184: ` || die'


I guess the only solution is to check the result of the test afterwards
with something like [ $? -eq 0 ] || die "frob failed"

Nikos Chantziaras wrote:

> It is indented with tabs, and the script runs OK on it's own.

How do you run an ebuild on its own? What commands did you try?