unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#41250: master build failure (invalid read syntax ?)
       [not found] ` <jwvblhfv175.fsf-monnier+emacs@gnu.org>
@ 2020-10-06 15:25   ` Andreas Schwab
  2020-10-07  7:34     ` Philippe Vaucher
  2020-10-07  7:36   ` Philippe Vaucher
  2020-10-07 15:55   ` Tassilo Horn
  2 siblings, 1 reply; 5+ messages in thread
From: Andreas Schwab @ 2020-10-06 15:25 UTC (permalink / raw)
  To: Stefan Monnier; +Cc: 41250, Philippe Vaucher, Emacs developers

On Okt 06 2020, Stefan Monnier wrote:

> I don't know how to reproduce the original proble

The problem only happens if you start with a pristine checkout of the
sources, or run make extraclean (which also deletes lisp/leim/ja-dic,
unlike make bootstrap), and you are lucky enough that lisp/leim/ja-dic
happens to be recreated before lisp/international/mule-util.elc.

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."





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#41250: master build failure (invalid read syntax ?)
  2020-10-06 15:25   ` bug#41250: master build failure (invalid read syntax ?) Andreas Schwab
@ 2020-10-07  7:34     ` Philippe Vaucher
  0 siblings, 0 replies; 5+ messages in thread
From: Philippe Vaucher @ 2020-10-07  7:34 UTC (permalink / raw)
  To: Andreas Schwab; +Cc: 41250, Stefan Monnier, Emacs developers

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

>
> > I don't know how to reproduce the original proble
>
> The problem only happens if you start with a pristine checkout of the
> sources, or run make extraclean (which also deletes lisp/leim/ja-dic,
> unlike make bootstrap), and you are lucky enough that lisp/leim/ja-dic
> happens to be recreated before lisp/international/mule-util.elc.
>

This is exactly how I build master: checkout the repo then autogen &&
configure && make.

Thanks, I'll watch #41250 then.
Philippe

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#41250: master build failure (invalid read syntax ?)
       [not found] ` <jwvblhfv175.fsf-monnier+emacs@gnu.org>
  2020-10-06 15:25   ` bug#41250: master build failure (invalid read syntax ?) Andreas Schwab
@ 2020-10-07  7:36   ` Philippe Vaucher
  2020-10-07 13:06     ` Stefan Monnier
  2020-10-07 15:55   ` Tassilo Horn
  2 siblings, 1 reply; 5+ messages in thread
From: Philippe Vaucher @ 2020-10-07  7:36 UTC (permalink / raw)
  To: 41250; +Cc: Emacs developers

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

>
> This has recently been addressed in `emacs` with a series of 3 commits
> each trying to fix it slightly differently.
> I don't know how to reproduce the original proble, so if it affects you,
> can you try the most recent `master` and see if it still affects you?
>

The recent changes has fixed the problem for me (
https://gitlab.com/Silex777/docker-emacs/-/pipelines/198745106)

Thanks,
Philippe

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#41250: master build failure (invalid read syntax ?)
  2020-10-07  7:36   ` Philippe Vaucher
@ 2020-10-07 13:06     ` Stefan Monnier
  0 siblings, 0 replies; 5+ messages in thread
From: Stefan Monnier @ 2020-10-07 13:06 UTC (permalink / raw)
  To: Philippe Vaucher; +Cc: 41250, Emacs developers

>> This has recently been addressed in `emacs` with a series of 3 commits
>> each trying to fix it slightly differently.
>> I don't know how to reproduce the original proble, so if it affects you,
>> can you try the most recent `master` and see if it still affects you?
> The recent changes has fixed the problem for me (
> https://gitlab.com/Silex777/docker-emacs/-/pipelines/198745106)

Good to hear, thank you,


        Stefan






^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#41250: master build failure (invalid read syntax ?)
       [not found] ` <jwvblhfv175.fsf-monnier+emacs@gnu.org>
  2020-10-06 15:25   ` bug#41250: master build failure (invalid read syntax ?) Andreas Schwab
  2020-10-07  7:36   ` Philippe Vaucher
@ 2020-10-07 15:55   ` Tassilo Horn
  2 siblings, 0 replies; 5+ messages in thread
From: Tassilo Horn @ 2020-10-07 15:55 UTC (permalink / raw)
  To: Stefan Monnier; +Cc: 41250, Philippe Vaucher, Emacs developers

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Since ~2 days the branch master refuses to build in my docker images,
>> is this known/normal?
>>
>> #38 435.6 Loading macroexp.elc...
>> #38 435.6 Invalid read syntax: "?"
>>
>> https://gitlab.com/Silex777/docker-emacs/-/jobs/774443194
>
> This has recently been addressed in `emacs` with a series of 3 commits
> each trying to fix it slightly differently.
> I don't know how to reproduce the original proble, so if it affects you,
> can you try the most recent `master` and see if it still affects you?

I had a similar "Invalid read syntax" error when doing `eval-buffer'
while AUCTeX' texmathp.el was opened (but didn't have time to report
it).  With the current master, it works again.

Bye,
Tassilo






^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-10-07 15:55 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAGK7Mr6T04nmWTMyYG53UA_tmPUFNZ-U46yCeXezoTWaKx+TEA@mail.gmail.com>
     [not found] ` <jwvblhfv175.fsf-monnier+emacs@gnu.org>
2020-10-06 15:25   ` bug#41250: master build failure (invalid read syntax ?) Andreas Schwab
2020-10-07  7:34     ` Philippe Vaucher
2020-10-07  7:36   ` Philippe Vaucher
2020-10-07 13:06     ` Stefan Monnier
2020-10-07 15:55   ` Tassilo Horn

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).