Date: Sun, 08 Oct 2017 21:10:45 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 222872] lang/ruby22: does not build with POSIX-compliant sh -c Message-ID: <bug-222872-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222872 Bug ID: 222872 Summary: lang/ruby22: does not build with POSIX-compliant sh -c Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ruby@FreeBSD.org Reporter: jilles@FreeBSD.org Blocks: 220587 Flags: maintainer-feedback?(ruby@FreeBSD.org) Assignee: ruby@FreeBSD.org Created attachment 187013 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187013&action= =3Dedit allow both current and POSIX-compliant sh -c The RB_SET_CONF_VAR macro uses a construct like sh -c 'command' -- arg0 arg1 and assume that $0 will expand to arg0 and $1 will expand to arg1. Our current sh implements it that way. However, POSIX specifies that $0 will expand to -- and $1 will expand to arg0, since the command string is an ope= rand and not an option-argument. Bug #220587 requests making sh POSIX-compliant = in this regard. If the argument after the command string does not start with '-', the curre= nt sh behaves as required by POSIX. Therefore, the macros should be adjusted so this is always the case. Tested with poudriere, stable/10 with patched head sh. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220587 [Bug 220587] /bin/sh Incorrect options handling --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222872-21402>