On 30 May 2012 05:56, Dan Shelton <[email protected]> wrote: > On 27 May 2012 20:59, Roland Mainz <[email protected]> wrote: >> Hi! >> >> ---- >> >> [This is AFAIK an issue once seen on Solaris... which got fixed... and >> now has it's revenge upon us on Linux... ;-( ] >> If I try to build ast-open.2012-05-18 on SuSE 12.1/AMD64 with ksh >> binary in $PATH (and SHELL pointing to it, too) previously fetched >> from a Solaris 12.1/AMD64 ast-open.2012-05-18 (with >> -DSHOPT_CMDLIB_BLTIN=0 -DSH_CMDLIB_DIR=\"/usr/ast/bin\" >> -DSHOPT_CMDLIB_HDR=\"/home/test001/work/ast_ksh_20120518/build_linux_32bit/tmp_gnulinux_builtin_header.h\" >> ; I've attached the header file as "tmp_gnulinux_builtin_header.h") >> build I get the following error: >> -- snip -- >> + chmod -w >> /home/test001/work/ast_ksh_20120518/build_normal_sed_under_valgrind/arch/linux.i386-64/lib/libcmd.so.1.2 >> ksh[783]: chmod: >> /home/test001/work/ast_ksh_20120518/build_normal_sed_under_valgrind/arch/linux.i386-64/lib/libcmd.so.1.2: >> not found [Invalid argument] >> -- snip -- >> >> Glenn/David: Can you reproduce the problem on your side (e.g. compile >> ast-open with the SHOPT_CMDLIB_HDR header attached to this file, fetch >> the resulting ksh93 binary and use it again to build ast-open) ? > > I can reproduce the problem on Fedora, too.
This bug is still present in ast-ksh and ast-open beta 20120531. AFAIK the only requirement to test this is to have the chmod builtin enabled by default. _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
