On Wed, 7 Mar 2018 07:44:41 +0100
Tito wrote:
> Deweloper could you post your .config?
>
Sure:
--
#
# Automatically generated make config: don't edit
# Busybox version: 1.29.0.git
# Mon Mar 5 18:33:54 2018
#
CONFIG_HAVE_DOT_CONFIG=y
#
# Settings
#
CONFIG_DESKTOP=y
CONFIG_EXTRA_COMPAT=y
CON
On Sat, 03 Mar 2018 23:18:46 +
"Laurent Bercot" wrote:
> >Not all systems have SA_RESTART, but signal_SA_RESTART_empty_mask()
> >is required to build busybox. This at least allows you to build on
> >systems without SA_RESTART.
>
> SA_RESTART is POSIX, and supported at the very least on L
> $ busybox ash -c "echo '/dev/nul'*"
> /dev/nul*
I do not know what POSIX says about this; but even if the behaviour does
not violate POSIX, I think most of us can agree that this is very
counter-intuitive and results in significant inconvenience?
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7
On Thu, Mar 08, 2018 at 10:55:40AM +0800, Casper Ti. Vector wrote:
> > $ busybox ash -c "echo '/dev/nul'*"
> > /dev/nul*
I found this issue to be present on busybox 1.28.0 on Void Linux, but
not on some other platforms. I will look into it...
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186
On Thu, Mar 08, 2018 at 11:10:05AM +0800, Casper Ti. Vector wrote:
> I found this issue to be present on busybox 1.28.0 on Void Linux, but
> not on some other platforms. I will look into it...
Issue reproduced successfully with CFLAGS='-O2' and busybox 1.28.1 (I
guess older versions are probably