all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Live System User <nyc4bos@aol.com>
To: emacs-devel@gnu.org
Subject: Re: The 'master' branch no longer compiles.
Date: Tue, 13 Nov 2018 11:47:44 -0500	[thread overview]
Message-ID: <87va50orf3.fsf@aol.com> (raw)
In-Reply-To: jwvr2fpazi5.fsf-monnier+gmane.emacs.devel@gnu.org

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

>> This didn't work for me, initially:
>>
>> [...]
>> make[2]: Entering directory '/tmp/emacs-27.0-git-master/lisp'
>>   ELC      emacs-lisp/gv.elc
>>   ELC      emacs-lisp/ring.elc
>>   ELC      net/tramp.elc
>>   ELC      net/tramp-cmds.elc
>>   ELC      mail/emacsbug.elc
>>   ELC      net/trampver.elc
>>   ELC      progmodes/xref.elc
>>   ELC      textmodes/css-mode.elc
>>
>> In end of data:
>> mail/emacsbug.el:489:1:Warning: the function ‘w32--os-description’ is not
>>     known to be defined.
>> make[2]: Leaving directory '/tmp/emacs-27.0-git-master/lisp'
>> make[1]: Leaving directory '/tmp/emacs-27.0-git-master/lisp'
>>  
>> This error occurred on Gnu/Linux.
>
> I don't see any error in the text you quoted.

  Indeed it's a warning, sorry.

  The "error" (warning) I am referring to is the fact that
  ‘w32--os-description’ is being reference at all (and if/when
  referenced, the "w32-fns.el" file should have been or caused
  to beloaded).

  Is it because it's not necessary during the dump process?

  Thanks.





  reply	other threads:[~2018-11-13 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  2:19 The 'master' branch no longer compiles aditya siram
2018-11-12  2:39 ` Paul Eggert
2018-11-12  3:36   ` Eli Zaretskii
2018-11-12 13:51     ` Stefan Monnier
2018-11-13  1:13       ` Live System User
2018-11-13 13:20         ` Stefan Monnier
2018-11-13 16:47           ` Live System User [this message]
2018-11-13 17:53             ` Eli Zaretskii
2018-11-13 13:56       ` Noam Postavsky
2018-11-13 14:08         ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87va50orf3.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.