-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
localedef: ../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion `ec >= 0' failed. #1878
Comments
The same error shows up when attempting to run Fish Shell on an alternative OS. Perhaps it's related somehow? |
Almost certainly the same problem. Arch uses newer glibc etc. See for example #1578. Still no strace.... |
While this is not for |
Hopefully this helps... #1306 (comment) |
For those who land here and don't know a lot about linux, unpacking the relevant file (e.g. |
Okay let's do this one. The crux is the following from man
On WSL the caller isn't being suspended. Actual fail in glibc is here, which got introduced Sept 28th with this commit. Test case below, which is a variation on #1005. It can be run on Xenial. Get the 'Oops' path on WSL but not Real Linux. No
|
I unpacked the relevant file, ran locale-gen, but still got this error when installing gtkd from the AUR (on WSL). Is there another locale I need to set beyond en_US.UTF-8? |
The same thing also happens when I use clang, from what I can tell. |
I ran into the same problem trying yocto project build in Ubuntu 16.04 in WSL: Written by Tom Tromey [email protected] Is there any get around in this issue? |
@derekyu56 - That's somewhat curious, if you are on 16.04 (Xenial). What does [edit] I didn't pick up on 'yocto build'. If yocto ships m4 make sure get that binary's version, not the one from Ubuntu Xenial. And if the yocto m4 binary is statically linked, then pretty much all bets are off. The work-around would be to use Xenial's m4 with Xenial's 2.23 glibc. |
Here are the version information: m4 (GNU M4) 1.4.17 I don't think Yocto shipped with m4. |
Sorry, I was wrong. Yocto did shipped with m4 and it is version 1.4.18. I will see if I can replace it with the one from Xenial. |
You can also try to find an older version of Yocto that uses glibc 2.23. [ |
Unfortunately, older version has different problems and I was not able to use that either. Thanks for the suggestion. I guess I will have to wait until this issue is resolved. |
@Christoph-Wagner That exactly helps! THX dude. |
What is needed to get this actually fixed? The workarounds are fine for each use-case, but it those aren't permanent solutions. I'm running into this issue when using NixOS, which uses m4. My guess is that eventually LTS distros will also run into these issues. |
@matshch Stick with 16.04 LTS for now. |
@matshch I'm on insider 17025 and sticking on 17.04 for now, no problem so far. |
Thanks, I will give a try.
…On Mon, Oct 30, 2017 at 2:46 PM, Adam Oleksy ***@***.***> wrote:
@derekyu56 <https://github.com/derekyu56> You can use newest yocto (e.g.
rocko) on WSL without this problem. There is only one thing you have to do:
git checkout ce7e0252c498c25c782e181283172591d3e8b76b -- meta/conf
/distro/include/yocto-uninative.inc
It changes version of the uninative package to the one which has glibc
which works on WSL.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1878 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIE6Sx7OE79Y8T_MmQsFHcC-8EC6jV3Gks5sxhlzgaJpZM4M50nV>
.
|
The yocto build still failed in rocko build with the git checkout. This
time it did build 1031 packages, much better than before but it failed in:
/home/derekyu/yocto/poky/meta/recipes-devtools/gcc/gcc-cross_7.2.bb:
do_compile
/home/derekyu/yocto/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb:
do_package
This is a different topic so I'll stop here. Thanks anyway.
…On Tue, Oct 31, 2017 at 10:18 PM, Derek Yu ***@***.***> wrote:
Thanks, I will give a try.
On Mon, Oct 30, 2017 at 2:46 PM, Adam Oleksy ***@***.***>
wrote:
> @derekyu56 <https://github.com/derekyu56> You can use newest yocto (e.g.
> rocko) on WSL without this problem. There is only one thing you have to do:
> git checkout ce7e0252c498c25c782e181283172591d3e8b76b -- meta/conf
> /distro/include/yocto-uninative.inc
> It changes version of the uninative package to the one which has glibc
> which works on WSL.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1878 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AIE6Sx7OE79Y8T_MmQsFHcC-8EC6jV3Gks5sxhlzgaJpZM4M50nV>
> .
>
|
@jstarks is the fix supposed to be included in 17035? Doesn't look like it for me :( |
No :(. We've had some unfortunate delays getting WSL fixes into the insider builds lately. We'll get that unblocked as soon as we can. |
Was this fixed in 17040 ? |
@nstrelow nope:
|
Windows Insider Build 17046 has improved CLONE_VFORK and CLONE_VM support. |
This is great news! Does this mean the behavior is fully compliant, or are there still incompatibilities left? |
|
The behavior is not yet fully compatible. There are still some flags including CLONE_NEWUSER and CLONE_SIGHAND that do not work, and some supported flag combinations that either are not 100% compatible or haven't yet been verified to be. Some of these we are already looking at and others will be prioritized, as per usual, when interesting scenarios emerge involving them. |
Just as a heads-up, this issue affects qemu-user as well: dpkg: warning: ignoring pre-dependency problem!
Preparing to unpack .../archives/bash_4.4-5_m68k.deb ...
preinst: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5_m68k.deb (--unpack):
new bash package pre-installation script subprocess was killed by signal (Aborted)
Selecting previously unselected package bsdutils.
dpkg: regarding .../bsdutils_1%3a2.30.2-0.1_m68k.deb containing bsdutils, pre-dependency problem:
bsdutils pre-depends on libsystemd0
libsystemd0 is not installed. qemu bug report is: https://bugs.launchpad.net/qemu/+bug/1673976 |
I'm also getting the same error with qemu-user
|
same error message here http://paste.ubuntu.com/26140607/ |
These errors are all expected pre-build 17046. If you see these errors on 17046 or newer, please let us know. |
For those of you not on the Insider channel, I made a workaround script. If you want to update to Ubuntu 17.10, that should do the trick, but be warned it could have unintended side effects in scenarios I haven't tested, and could cause problems when you do eventually receive the fix from Microsoft. |
When running
locale-gen
it always failed with the following assertion failure:This is because by default charmaps (/usr/share/i18n/charmaps) are gzipped and localedef invokes posix_spawn in order to decompress those files.
Expected results
No errors when running locale-gen with gzipped charmap files.
Actual results (with terminal output if applicable)
localedef: ../sysdeps/unix/sysv/linux/spawni.c:360: __spawnix: Assertion
ec >= 0' failed.`Your Windows build number
15063
Steps / All commands required to reproduce the error from a brand new installation
/etc/locale.gen
.Strace of the failing command
None. This bug is easy to be reproduced and the line numbers are available.
Required packages and commands to install
glibc 2.25
The text was updated successfully, but these errors were encountered: