Bug 1564201 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Mike Hommey [:glandium] from comment #2)
> FWIW, when I try with some (valid) japanese characters, the build fails while creating the virtualenv, during configure, meaning it went that far. Your build seems to have gone past that, and to have a config.status that it can't read.

Ah, I realise the issue now. I have a built objdir and renamed it to have a non-ascii character in its name (») and then attempted to rebuild and it was this that failed. When I try with an empty objdir I get the virtualenv issue instead.
Revision 1 by
on 
(In reply to Mike Hommey [:glandium] from comment #2)
> FWIW, when I try with some (valid) japanese characters, the build fails while creating the virtualenv, during configure, meaning it went that far. Your build seems to have gone past that, and to have a config.status that it can't read.

Ah, I realise the issue now. I had a built objdir and renamed it to have a non-ascii character in its name (») and then attempted to rebuild and it was this that failed. When I try with an empty objdir I get the virtualenv issue instead.

Back to Bug 1564201 Comment 3