Re: [perl #133495] perl-5.28.0 fails to build on Solaris 10: Re: pkg/53568: perl-5.28.0 fails to build on Solaris 10

[Hiroshi Hakoyama <hako%affrc.go.jp@localhost>]

I found a workaround:
A build with CFLAGS+= -O2 -mcpu=ultrasparc3 -mtune=ultrasparc3 was OK.
Optimization level -O3 causes the problem.

> Can you run that miniperl command (or possibly any small one-liner) in
> a debugger and give us a backtrace? That should give us much more
> information on what's happening here.
> 
> Leon

Please see the following result:

# dbx ./miniperl core
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
Reading miniperl
dbx: warning: unknown location expression code (0xf2)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
dbx: warning: unknown location expression code (0x9e)
core file header read successfully
Reading ld.so.1
Reading libm.so.2
Reading libdl.so.1
Reading libsocket.so.1
Reading libnsl.so.1
Reading libpthread.so.1
Reading librt.so.1
Reading libssp.so.0.0.0
Reading libc.so.1
Reading libaio.so.1
Reading libmd.so.1
Reading libgcc_s.so.1
Reading libc_psr.so.1
t@1 (l@1) program terminated by signal BUS (invalid address alignment)
0x000ecf6c: Perl_hv_common+0x156c:      ld       [%g3], %o0
(dbx) where                                                                  
current thread: t@1
=>[1] Perl_hv_common(0x5b65439d, 0x338818, 0x0, 0xffbffaaa, 0x33d1e8, 0x0), at 0xecf6c 
  [2] Perl_hv_common_key_len(0x29bba8, 0x338818, 0xffbffaaa, 0x19, 0x8, 0x0), at 0xee2f0 
  [3] S_init_postdump_symbols(0x29bba8, 0x338818, 0xffbffac3, 0xffbfede0, 0x19, 0xffbffaaa), at 0x5765c 
  [4] perl_parse(0x0, 0x334290, 0x339820, 0xffbfece0, 0x1, 0x338758), at 0x5c758 
  [5] main(0x4, 0xffbfecd4, 0xffbfece8, 0x2959b8, 0xff170100, 0x0), at 0x1bd9dc 
(dbx) quit
dbx: internal warning: td_ta_clear_event() failed -- debugger service failed
dbx: internal warning: td_ta_sync_tracking_enable(0) failed -- debugger service failed

> 2018/09/03 23:30、Leon Timmermans via RT <perlbug-followup%perl.org@localhost>のメール:
> 
> On Mon, Sep 3, 2018 at 5:34 AM Hiroshi Hakoyama (via RT)
> <perlbug-followup%perl.org@localhost> wrote:
>> 
>> # New Ticket Created by  Hiroshi Hakoyama
>> # Please include the string:  [perl #133495]
>> # in the subject line of all future correspondence about this issue.
>> # <URL: https://rt.perl.org/Ticket/Display.html?id=133495 >
>> 
>> 
>> This is a bug report for perl from hako%affrc.go.jp@localhost,
>> generated with the help of perlbug 1.40 running under perl 5.26.2.
>> 
>> 
>> -----------------------------------------------------------------
>> [Please describe your issue here]
>> perl-5.28.0 fails to build on Solaris 10.
>> I send this bug report with an advice from Benny, gnats-bugs%netbsd.org@localhost.
>> Thanks in advance.
>> 
>> Hiroshi Hakoyama
>> 
>> The following reply was made to PR pkg/53568; it has been noted by GNATS.
>> 
>> From: Benny Siegert <bsiegert%gmail.com@localhost>
>> To: gnats-bugs%netbsd.org@localhost
>> Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost
>> Subject: Re: pkg/53568: perl-5.28.0 fails to build on Solaris 10
>> Date: Sun, 2 Sep 2018 16:06:27 +0000
>> 
>> perl-5.28.0 fails to build on Solaris 10. perl-5.26.2 was OK.
>> 
>> ...
>> gcc -c -DPERL_CORE -D_REENTRANT -O3 -mcpu=3Dultrasparc3 -mtune=3Dultraspa=
>> rc3 -D_FORTIFY_SOURCE=3D2 -pthread -I/usr/include -fwrapv -fno-strict-alias=
>> ing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64=
>> -DPERL_USE_SAFE_PUTENV -O3 -mcpu=3Dultrasparc3 -mtune=3Dultrasparc3 -D_FOR=
>> TIFY_SOURCE=3D2 -pthread -I/usr/include -Wall -Werror=3Ddeclaration-after-s=
>> tatement -Werror=3Dpointer-arith -Wextra -Wc++-compat -Wwrite-strings -fPIC=
>> miniperlmain.c
>> gcc -pthread -L/usr/lib -Wl,-R/usr/lib -Wl,-R/usr/pkg/lib -o miniperl  op=
>> mini.o perlmini.o  gv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o r=
>> eentr.o mro_core.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp=
>> _ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o gl=
>> obals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o=
>>  caretx.o dquote.o time64.o  miniperlmain.o  -lm -ldl -lsocket -lnsl -lpthr=
>>  ead -lrt
>>  LD_LIBRARY_PATH=3D/usr/pkgsrc/lang/perl5/work/perl-5.28.0 ./miniperl -w -=
>>  Ilib -Idist/Exporter/lib -MExporter -e '<?>' || sh -c 'echo >&2 Failed to b=
>>  uild miniperl.  Please run make minitest; exit 1'
>>  /usr/bin/bash: line 1: 28934 Bus Error                (core dumped) LD_LIB=
>>  RARY_PATH=3D/usr/pkgsrc/lang/perl5/work/perl-5.28.0 ./miniperl -w -Ilib -Id=
>>  ist/Exporter/lib -MExporter -e '<?>'
>>  Failed to build miniperl. Please run make minitest
>>  *** Error code 1
>> 
>>  This sounds like an upstream regression. Please file a bug report
>>  upstream (bugs.perl.org) and send a link to this list.
>> 
>>  --=20
>>  Benny
> 
> Given that that is a SPARC machine, and you're receiving a SIGBUS,
> this is probably an alignment issue (and thus being sparc specific,
> not solaris specific).
> 
> Can you run that miniperl command (or possibly any small one-liner) in
> a debugger and give us a backtrace? That should give us much more
> information on what's happening here.
> 
> Leon
>