Re: Can't compile perl5 on Soalris 10

Hi,

actually there is no empty files... there is simply no files at all :

[root@zone2 perl5]$ ls -lh /var/tmp/pkgbuild/lang/perl5/work/.error
total 0
[root@zone2 perl5]$ ls -lh /var/tmp/pkgbuild/lang/perl5/work/.warning
total 0

However there is something there :

[root@zone2 perl5]$ cat /var/tmp/pkgbuild/lang/perl5/work/.error-done/_check-interpreter
[check-interpreter.mk] The interpreter "perl" of "/var/tmp/pkgbuild/lang/perl5/work/.destdir/usr/pkg/lib/perl5/5.28.0/Math/BigFloat/Trace.pm" does not exist.
[check-interpreter.mk] The interpreter "perl" of "/var/tmp/pkgbuild/lang/perl5/work/.destdir/usr/pkg/lib/perl5/5.28.0/Math/BigInt/Trace.pm" does not exist.

[root@zone2 perl5]$ head -1 "/var/tmp/pkgbuild/lang/perl5/work/.destdir/usr/pkg/lib/perl5/5.28.0/Math/BigInt/Trace.pm"
#!perl
[root@zone2 perl5]$ head -1 "/var/tmp/pkgbuild/lang/perl5/work/.destdir/usr/pkg/lib/perl5/5.28.0/Math/BigFloat/Trace.pm"
#!perl

I'll try to take a look to mk/bsd.pkg.mk.

On Thu, Feb 28, 2019 at 3:20 PM Roland Illig <roland.illig%gmx.de@localhost> wrote:

Am 25.02.2019 um 18:15 schrieb Julien Savard:
> cd /var/tmp/pkgbuild/lang/perl5/work/.error;
>    for file in ./*; do
>    test "$file" != "./*" || exit 0;
> break; done;
>    /usr/bin/cat * |
> /usr/pkg/bin/nbsed -e "s|^|ERROR: |" 1>&2;
>    if /usr/pkg/bin/nawk 'END { exit (NR > 0) ? 0 : 1; }'
> ./*; then /usr/bin/mv -f ./*
> /var/tmp/pkgbuild/lang/perl5/work/.error-done;
>   exit 1; fi
> *** Error code 1

Please have a look at the files in
/var/tmp/pkgbuild/lang/perl5/work/.error and
/var/tmp/pkgbuild/lang/perl5/work/.warning. I suspect that there is an
empty file there.

These files are created by ${ERROR_MSG}, ${FAIL_MSG} and ${WARNING_MSG}.
These commands are defined in mk/bsd.pkg.mk. To further analyze this,
you may override these with a custom command that pauses until you press
Enter. Then you will see exactly at which point these files are written.

The actual cause might be an error message that has a shell redirection
in it, such as:

${ERROR_MSG} Cannot continue -> stopping.

This would interpret the ">" as a shell redirection. That's my first
guess, it may also be something entirely different.

Best,
Roland