Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Oct 2017 21:10:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        ruby@FreeBSD.org
Subject:   maintainer-feedback requested: [Bug 222872] lang/ruby22: does not build with POSIX-compliant sh -c
Message-ID:  <bug-222872-21402-VpaJjZQq0Q@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222872-21402@https.bugs.freebsd.org/bugzilla/>
References:  <bug-222872-21402@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
Jilles Tjoelker <jilles@FreeBSD.org> has reassigned Bugzilla Automation
<bugzilla@FreeBSD.org>'s request for maintainer-feedback to ruby@FreeBSD.or=
g:
Bug 222872: lang/ruby22: does not build with POSIX-compliant sh -c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222872



--- Description ---
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222872-21402-VpaJjZQq0Q>