Re: W3C compliance: a novel response

So much this. *phm* On Sat, Mar 11, 2017 at 2:18 PM, Lee wrote: > On 3/11/17, Paul B. Gallagher wrote: > > When I complained about bad browser sniffing at one of my favorite > > websites: > > > >> I've never understood why web designers prefer to waste time writing > >> s

Re: Cannot compile 2.46

mozconfig or .mozconfig > need to be there. > > FRG > > P. H. Madore wrote: > >> Here is moz.configure: >> >> # -*- Mode: python; c-basic-offset: 4; indent-tabs-mode: nil; tab-width: >> 40 >> -*- >> # vim: set filetype=python: >> # This Source

Re: Cannot compile 2.46

ake client.mk checkout in the 2.46 comm-release dir? > > FRG > > P. H. Madore wrote: > >> This is a new issue for me. I was using 2.40 until today. Now I can't use >> anything. Something about "old-configure." Here is the complete >> configuration lo

Re: Cannot compile 2.46

I'm not sure what my mozconfig is like. How do I find out? I hadn't had this problem before. *phm* <http://phmadore.com> On Wed, Mar 8, 2017 at 7:45 PM, Edmund Wong wrote: > P. H. Madore wrote: > > This is a new issue for me. I was using 2.40 until today. Now

Cannot compile 2.46

This is a new issue for me. I was using 2.40 until today. Now I can't use anything. Something about "old-configure." Here is the complete configuration log: Reexecuting in the virtualenv checking for a shell... /bin/sh checking for host system type... x86_64-pc-linux-gnu checking for target system