Weird compilation bug just started appearing

Weird compilation bug just started appearing

[Lars Ingebrigtsen]

I'm getting:

make[2]: Entering directory '/home/larsi/src/emacs/trunk/lisp'
  ELC      auth-source.elc

In toplevel form:
auth-source.el:42:1:Error: Wrong type argument: symbolp, 2.0
Makefile:296: recipe for target 'auth-source.elc' failed
make[2]: *** [auth-source.elc] Error 1
make[2]: Leaving directory '/home/larsi/src/emacs/trunk/lisp'
Makefile:319: recipe for target 'compile-main' failed
make[1]: *** [compile-main] Error 2
make[1]: Leaving directory '/home/larsi/src/emacs/trunk/lisp'
Makefile:411: recipe for target 'lisp' failed
make: *** [lisp] Error 2

This is after a fresh checkout...  but I'm only getting it on one
laptop -- the other machine's tree is fine.

And both trees are fresh checkouts.  Both machines are Debian 9
machines.

I must have borked something up somewhere...  or is anybody else also
seeing this?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Weird compilation bug just started appearing

[Richard Copley]

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Tue, 9 Jul 2019 at 20:09, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> I'm getting:
>
> make[2]: Entering directory '/home/larsi/src/emacs/trunk/lisp'
>   ELC      auth-source.elc
>
> In toplevel form:
> auth-source.el:42:1:Error: Wrong type argument: symbolp, 2.0
> Makefile:296: recipe for target 'auth-source.elc' failed
> make[2]: *** [auth-source.elc] Error 1
> make[2]: Leaving directory '/home/larsi/src/emacs/trunk/lisp'
> Makefile:319: recipe for target 'compile-main' failed
> make[1]: *** [compile-main] Error 2
> make[1]: Leaving directory '/home/larsi/src/emacs/trunk/lisp'
> Makefile:411: recipe for target 'lisp' failed
> make: *** [lisp] Error 2
>
> This is after a fresh checkout...  but I'm only getting it on one
> laptop -- the other machine's tree is fine.
>
> And both trees are fresh checkouts.  Both machines are Debian 9
> machines.
>
> I must have borked something up somewhere...  or is anybody else also
> seeing this?
>

I see something similar.

make[2]: Entering directory '/c/projects/emacs/lisp'
  ELC      textmodes/css-mode.elc

In toplevel form:
textmodes/css-mode.el:37:1:Error: Wrong type argument: symbolp, 2.0

[-- Attachment #2: Type: text/html, Size: 1665 bytes --]

Re: Weird compilation bug just started appearing

[Lars Ingebrigtsen]

Richard Copley <rcopley@gmail.com> writes:

> In toplevel form:
> textmodes/css-mode.el:37:1:Error: Wrong type argument: symbolp, 2.0 

I found the error -- my fault.  Trunk should be OK again now.

I had said

(make-obsolete-variable json-pretty-print-max-secs nil "27.1")

and this didn't raise an error in the compilation of json.el, but
instead errored out with that message when you tried to compile some of
the other .el files...

Perhaps make-obsolete-variable should signal an error here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Weird compilation bug just started appearing

[Richard Copley]

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

On Tue, 9 Jul 2019 at 20:35, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Richard Copley <rcopley@gmail.com> writes:
>
> > In toplevel form:
> > textmodes/css-mode.el:37:1:Error: Wrong type argument: symbolp, 2.0
>
> I found the error -- my fault.  Trunk should be OK again now.
>

Thanks, works for me.

I had said
>
> (make-obsolete-variable json-pretty-print-max-secs nil "27.1")
>

I assume it's perfectly obvious to everyone else what is supposed to be
wrong with that. For my benefit, would you mind saying it explicitly,
please?


> and this didn't raise an error in the compilation of json.el, but
> instead errored out with that message when you tried to compile some of
> the other .el files...
>
> Perhaps make-obsolete-variable should signal an error here?
>

Presumably!

[-- Attachment #2: Type: text/html, Size: 1611 bytes --]

Re: Weird compilation bug just started appearing

[Lars Ingebrigtsen]

Richard Copley <rcopley@gmail.com> writes:

>  (make-obsolete-variable json-pretty-print-max-secs nil "27.1")
>
> I assume it's perfectly obvious to everyone else what is supposed to be wrong
> with that. For my benefit, would you mind saying it explicitly, please?

That should be

(make-obsolete-variable 'json-pretty-print-max-secs nil "27.1")

otherwise I'm trying to obsolete the value of that variable, which was
2.0.  :-/

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Weird compilation bug just started appearing

[Andreas Schwab]

On Jul 09 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Perhaps make-obsolete-variable should signal an error here?

It does, when executed.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Re: Weird compilation bug just started appearing

[Lars Ingebrigtsen]

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Jul 09 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
>> Perhaps make-obsolete-variable should signal an error here?
>
> It does, when executed.

Oh, yeah, so it does.  So this was basically just something requiring
something that required something that loaded json.elc, and that gave
the error?  Makes sense.  Then there's nothing to fix here.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no