Re: Watch out for build issues on non-Unicode systems

2019-08-22 Thread Mike Hommey
On Thu, Aug 22, 2019 at 02:42:48PM +0200, Nihanth Subramanya wrote: > Note that the config.status changes in bug 844509 seem to break `$./mach > clobber` - I had to manually rm -rf my objdir. Filed as bug 1575959, fixed on mozilla-central. Sorry for the annoyance. Mike > On Thu, Aug 22, 2019

Re: Watch out for build issues on non-Unicode systems

2019-08-22 Thread Jonathan Kew
On 22/08/2019 13:42, Nihanth Subramanya wrote: Note that the config.status changes in bug 844509 seem to break `$./mach clobber` - I had to manually rm -rf my objdir. Ah, that'll be what just happened to me, too. (Not just ./mach clobber, I was getting the same failure with ./mach build as

Re: Watch out for build issues on non-Unicode systems

2019-08-22 Thread Nihanth Subramanya
To clarify: it only breaks the clobber of an existing old objdir. Clobbering works fine henceforth. On Thu, Aug 22, 2019 at 2:42 PM Nihanth Subramanya wrote: > Note that the config.status changes in bug 844509 seem to break `$./mach > clobber` - I had to manually rm -rf my objdir. > > On Thu,

Re: Watch out for build issues on non-Unicode systems

2019-08-22 Thread Nihanth Subramanya
Note that the config.status changes in bug 844509 seem to break `$./mach clobber` - I had to manually rm -rf my objdir. On Thu, Aug 22, 2019 at 2:35 AM Mike Hommey wrote: > Hi, > > In bug 1575135 and bug 844509, we've changed how configure handles > strings from files and subprocesses, to