On Thu, Mar 14, 2013 at 4:48 PM, Michal Hlavinka <[email protected]> wrote: > On 03/14/2013 03:25 PM, ольга крыжановская wrote: >> On Thu, Mar 14, 2013 at 3:22 PM, Michal Hlavinka <[email protected]> >> wrote: >>> I just found out that ksh 2013-02-14, 2013-02-22 can't build ksh. >>> Version 2012-11-22 works fine. >>> >>> When building ksh with 2013-02-?? in the environment, build fails: >>> + iffe -v -X ast -X std -c 'cc -D_BLD_DLL -fPIC -D_BLD_ast -O2 -g -pipe >>> -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector >>> --param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing >>> -Wno-unknown-pragmas -Wno-parentheses -Wno-unused >>> -Wno-unused-but-set-variable -Wno-cpp ' run >>> >>> /mnt/home2/mhlavink/gitf/ksh/ksh-20130214/src/lib/libast/features/standards >>> iffe: cc -D_BLD_DLL -fPIC -D_BLD_ast -O2 -g -pipe -Wall >>> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector >>> --param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing >>> -Wno-unknown-pragmas -Wno-parentheses -Wno-unused >>> -Wno-unused-but-set-variable -Wno-cpp -c ./Fkrle7636.c >>> iffe: line 38: 7639: Memory fault(coredump) >>> >>> Every iffe cc ends with sigsegv. >>> >>> >>> It happens when building using rpmbuild. Manual build does not seem to >>> trigger this. >>> >>> Backtrace is: >>> #0 fcfopen (f=0x7f936cbe5540) at sh/fcin.c:64 >>> #1 sh_parse (shp=0x7fe480 <sh>, iop=0x7f936cbe5540, flag=0) at >>> sh/parse.c:350 >>> #2 exfile (shp=0x7fe480 <sh>, iop=0x7f936cbe5540, fno=11) at >>> sh/main.c:570 >>> #3 sh_main (ac=3, av=0x7ffffc2a2a98, userinit=0x0) at sh/main.c:360 >>> #4 main (argc=3, argv=0x7ffffc2a2a98) at sh/pmain.c:45 >>> >>> full backtrace is attached >> >> Michal, can you make a small stand alone script, without using >> rpmbuild, so we can reproduce this our selves, please? > > OK, I found out what is the difference, but I have no idea why it should > matter. > > What rpmbuild does: > rm -rf ksh-20130214 > /usr/bin/mkdir -p ksh-20130214 > cd ksh-20130214 > /usr/bin/gzip -dc ../ast-ksh.2013-02-14.tgz | /usr/bin/tar -xf - > /usr/bin/gzip -dc ../INIT.2013-02-14.tgz | /usr/bin/tar -xf - > /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . > export CC=gcc > ./bin/package make > > The difference is export CC=gcc, when present, it crashes, when omitted, it > works.
Does the crash no away if you specify the full path of "gcc" ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
