<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Current libinput git master doesn't handle paths with spaces in them like it used to" href="https://bugs.freedesktop.org/show_bug.cgi?id=101361#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Current libinput git master doesn't handle paths with spaces in them like it used to" href="https://bugs.freedesktop.org/show_bug.cgi?id=101361">bug 101361</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>That looks like a false positive too, sorry. That patch doesn't do anything with the build system, it's just the first one after the one we skipped to (the one that fixed the udev linker error). But if e9fc59efc853485cb builds fine and 1603a4326a6e7e819 breaks, then at least we know it's a libinput bug. Can you bisect again between those two? if the build fails add the changes from 56ceac34d0f42f7f9 and ce12ea6f9a0 manually and build again. If that too fails or it succeeds, do a git checkout -f (to get rid of the local changes) or git stash (if you know how to handle stashes), then git bisect bad/good depending on the outcome and hopefully this should tell us the real commit then.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>