| Summary: | Gatesgarth no longer building under WSL2 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | yoctoproject |
| Component: | bitbake | Assignee: | Anuj Mittal <anuj.mittal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie, yoctoproject |
| Version: | 3.2.2 | ||
| Target Milestone: | 3.3 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
yoctoproject
2021-01-04 14:20:58 UTC
That sounds like pseudo aborting for some reason as linux-libc-headers is the first task it would run under pseudo. Can you look WORKDIR/pseudo/pseudo.log and see if that gives any more of a clue about what happened? Indeed, there's something: $ cat pseudo/pseudo.log debug_logfile: fd 2 pid 14987 [parent 14986], doing new pid setup and server start Setup complete, sending SIGUSR1 to pid 14986. path mismatch [2 links]: ino 2207517 db '/run/shm/sem.mp-nh9e4dot' req '/run/shm/af4ZYg'. So I tried some things. According to https://docs.yoctoproject.org/ref-manual/migration-3.2.html#pseudo-path-filtering-and-mismatch-behaviour I should either use the PSEUDO_DEBUG = "nfoPcvdDyerpswikVx" flag (which doesn't seem to do anything... bummer) or use PSEUDO_IGNORE_PATHS. I did both, and the later gives me another error which might indicate a bigger problem? pid 25910 [parent 25909], doing new pid setup and server start Setup complete, sending SIGUSR1 to pid 25909. path mismatch [5 links]: ino 372550 db '/tmp/tmp.eMUNKdTbkP/build/tmp/work/core2-64-poky-linux/linux-libc-headers/5.8-r0/recipe-sysroot-native/etc/terminfo/v/vt200' req '/tmp/tmp.eMUNKdTbkP/build/tmp/sysroots-components/x86_64/ncurses-native/etc/terminfo/v/vt220'. Is there a way to be less restrictive with pseudo like it behaved in 3.1? If not, what is needed to solve this problem. It is a big problem right now, because I wanted to migrate onto gatesgarth this week. A temporary fix might be to try adding: PSEUDO_IGNORE_PATHS_append = ":/run/" (or add :/run/ to PSEUDO_IGNORE_PATHS in bitbake.conf) sorry, it should be ",/run/" as its comma delimited. I think we may need to add /run/ to the defaults as the real fix... (In reply to comment #5) > sorry, it should be ",/run/" as its comma delimited. I think we may need to > add /run/ to the defaults as the real fix... That seems to do the trick! Yeah, I guess /run/ should be in the default exclude, but I don't know why it only happens on WSL (I assume you have tested other linux distributions ;) ). And it *always* happened, even on a clean WSL debian distro. Thanks for your help! I've sent a patch to the mailing list and will add it for testing in master-next. Reassign to Anuj for gatesgarth backport |