unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Re: Build Failure
       [not found]           ` <1024063905.30056@sj-nntpcache-5>
@ 2002-06-15 14:13             ` Richard Stallman
  0 siblings, 0 replies; 9+ messages in thread
From: Richard Stallman @ 2002-06-15 14:13 UTC (permalink / raw)
  Cc: emacs-devel

What compiler are you using?  Maybe -g has an effect other than
adding debugging information.

It is also possible that unexec manages to handle one case
and not the other.

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

* build failure
@ 2009-10-26 16:33 Sean Sieger
  2009-10-27 17:29 ` Glenn Morris
  0 siblings, 1 reply; 9+ messages in thread
From: Sean Sieger @ 2009-10-26 16:33 UTC (permalink / raw)
  To: emacs-devel

I just now did cvs update ...

make[2]: *** No rule to make target
`/home/sean/emacs/lisp/cedet/cedet-cscope.elc', needed by
`compile-main'.  Stop.
make[2]: Leaving directory `/home/sean/emacs/lisp'
make[1]: *** [lisp] Error 2
make[1]: Leaving directory `/home/sean/emacs'
make: *** [bootstrap] Error 2





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

* Re: build failure
  2009-10-26 16:33 Sean Sieger
@ 2009-10-27 17:29 ` Glenn Morris
  2009-10-27 18:35   ` Sean Sieger
  0 siblings, 1 reply; 9+ messages in thread
From: Glenn Morris @ 2009-10-27 17:29 UTC (permalink / raw)
  To: Sean Sieger; +Cc: emacs-devel

Sean Sieger wrote:

> I just now did cvs update ...
>
> make[2]: *** No rule to make target
> `/home/sean/emacs/lisp/cedet/cedet-cscope.elc', needed by
> `compile-main'.  Stop.

Crystal ball says:
always use `cvs update -dP', as documented in INSTALL.CVS.




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

* Re: build failure
  2009-10-27 17:29 ` Glenn Morris
@ 2009-10-27 18:35   ` Sean Sieger
  0 siblings, 0 replies; 9+ messages in thread
From: Sean Sieger @ 2009-10-27 18:35 UTC (permalink / raw)
  To: emacs-devel


    Crystal ball says:
    always use `cvs update -dP', as documented in INSTALL.CVS.

Thank you for causing me to read that, Glenn.





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

* build failure
@ 2013-11-12 13:36 Sean Sieger
  2013-11-12 14:56 ` Bastien
  0 siblings, 1 reply; 9+ messages in thread
From: Sean Sieger @ 2013-11-12 13:36 UTC (permalink / raw)
  To: emacs-devel@gnu.org

/bin/makeinfo --force -I./../emacs --no-split -o ../../info/org.info ./org.texi
./org.texi:6: @include `org-version.inc': No such file or directory.
./org.texi:278: warning: undefined flag: VERSION.
./org.texi:309: warning: undefined flag: VERSION.
make[3]: *** [../../info/org.info] Error 1
make[3]: Leaving directory `/c/trunk/doc/misc'
make[2]: *** [misc-info] Error 2
make[2]: Leaving directory `/c/trunk'
make[1]: *** [info] Error 2
make[1]: Leaving directory `/c/trunk'
make: *** [bootstrap] Error 2



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

* Re: build failure
  2013-11-12 13:36 build failure Sean Sieger
@ 2013-11-12 14:56 ` Bastien
  0 siblings, 0 replies; 9+ messages in thread
From: Bastien @ 2013-11-12 14:56 UTC (permalink / raw)
  To: Sean Sieger; +Cc: emacs-devel@gnu.org

Sean Sieger <sean.sieger@gmail.com> writes:

> /bin/makeinfo --force -I./../emacs --no-split -o ../../info/org.info ./org.texi
> ./org.texi:6: @include `org-version.inc': No such file or directory.
> ./org.texi:278: warning: undefined flag: VERSION.
> ./org.texi:309: warning: undefined flag: VERSION.
> make[3]: *** [../../info/org.info] Error 1
> make[3]: Leaving directory `/c/trunk/doc/misc'
> make[2]: *** [misc-info] Error 2
> make[2]: Leaving directory `/c/trunk'
> make[1]: *** [info] Error 2
> make[1]: Leaving directory `/c/trunk'
> make: *** [bootstrap] Error 2

Fixed, thanks.

-- 
 Bastien



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

* Build failure
@ 2019-09-21 14:21 John
  2019-09-21 15:27 ` Lars Ingebrigtsen
  0 siblings, 1 reply; 9+ messages in thread
From: John @ 2019-09-21 14:21 UTC (permalink / raw)
  To: emacs-devel

On one of my computers (running openSuSE GNU/Linux) building from master
fails with

^[7^[]2;jpff on cage: /home/jpff/GNU/emacs\a^[]1;cage\a^[8
^[[4mcage^[[24m:^[[1m~/GNU/emacs^[[0m> 

^[[4mcage^[[24m:^[[1m~/GNU/emacs^[[0m> make 

make -C lib all
make[1]: Entering directory '/home/jpff/GNU/emacs/lib'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/jpff/GNU/emacs/lib'
make -C lib-src all
make[1]: Entering directory '/home/jpff/GNU/emacs/lib-src'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/jpff/GNU/emacs/lib-src'
make -C src VCSWITNESS='$(srcdir)/../.git/logs/HEAD' all
make[1]: Entering directory '/home/jpff/GNU/emacs/src'
make -C ../admin/charsets all
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/charsets'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/charsets'
make -C ../admin/unidata charscript.el
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/unidata'
make[2]: Nothing to be done for 'charscript.el'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/unidata'
make -C ../admin/unidata all EMACS="../../src/bootstrap-emacs"
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/unidata'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/unidata'
make -C ../admin/charsets cp51932.el
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/charsets'
make[2]: Nothing to be done for 'cp51932.el'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/charsets'
make -C ../admin/charsets eucjp-ms.el
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/charsets'
make[2]: Nothing to be done for 'eucjp-ms.el'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/charsets'
make[1]: Leaving directory '/home/jpff/GNU/emacs/src'
make -C lisp all
make[1]: Entering directory '/home/jpff/GNU/emacs/lisp'
make -C ../leim all EMACS="../src/emacs"
make[2]: Entering directory '/home/jpff/GNU/emacs/leim'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/leim'
make -C ../admin/grammars all EMACS="../../src/emacs"
make[2]: Entering directory '/home/jpff/GNU/emacs/admin/grammars'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/jpff/GNU/emacs/admin/grammars'
make[2]: Entering directory '/home/jpff/GNU/emacs/lisp'
  ELC      gnus/gnus-agent.elc
Eager macro-expansion failure: (file-error "Testing file" "Permission denied" "/etc/news/organization")

In toplevel form:
gnus/gnus-agent.el:26:1:Error: Testing file: Permission denied, /etc/news/organization
make[2]: *** [Makefile:296: gnus/gnus-agent.elc] Error 1
make[2]: Leaving directory '/home/jpff/GNU/emacs/lisp'
make[1]: *** [Makefile:319: compile-main] Error 2
make[1]: Leaving directory '/home/jpff/GNU/emacs/lisp'
make: *** [Makefile:411: lisp] Error 2
^[[4mcage^[[24m:^[[1m~/GNU/emacs^[[0m> exit


Script done on 2019-09-21 15:15:14+01:00 [COMMAND_EXIT_CODE="0"]


It happens in gnus and org,  either of which I actually use.  What
does it mean?  I have other computers running the same OS which seem OK.
==John ffitch



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

* Re: Build failure
  2019-09-21 14:21 Build failure John
@ 2019-09-21 15:27 ` Lars Ingebrigtsen
  2019-09-21 19:10   ` Paul Eggert
  0 siblings, 1 reply; 9+ messages in thread
From: Lars Ingebrigtsen @ 2019-09-21 15:27 UTC (permalink / raw)
  To: John; +Cc: emacs-devel

John <jpff@codemist.co.uk> writes:

> It happens in gnus and org,  either of which I actually use.  What
> does it mean?  I have other computers running the same OS which seem OK.

It's a known problem in file-readable-p; it's being worked on.  See
bug#37475.

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



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

* Re: Build failure
  2019-09-21 15:27 ` Lars Ingebrigtsen
@ 2019-09-21 19:10   ` Paul Eggert
  0 siblings, 0 replies; 9+ messages in thread
From: Paul Eggert @ 2019-09-21 19:10 UTC (permalink / raw)
  To: Lars Ingebrigtsen, John; +Cc: emacs-devel

On 9/21/19 8:27 AM, Lars Ingebrigtsen wrote:
> It's a known problem in file-readable-p; it's being worked on.  See
> bug#37475.

Should be fixed now.



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

end of thread, other threads:[~2019-09-21 19:10 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-21 14:21 Build failure John
2019-09-21 15:27 ` Lars Ingebrigtsen
2019-09-21 19:10   ` Paul Eggert
  -- strict thread matches above, loose matches on Subject: below --
2013-11-12 13:36 build failure Sean Sieger
2013-11-12 14:56 ` Bastien
2009-10-26 16:33 Sean Sieger
2009-10-27 17:29 ` Glenn Morris
2009-10-27 18:35   ` Sean Sieger
     [not found] <1020431829.514859@sj-nntpcache-5>
     [not found] ` <3CD2B8A1.E3BAC47@is.elta.co.il>
     [not found]   ` <1020772560.927220@sj-nntpcache-5>
     [not found]     ` <8296-Tue07May2002175828+0300-eliz@is.elta.co.il>
     [not found]       ` <1020784405.676466@sj-nntpcache-3>
     [not found]         ` <ygahelju908.fsf@jupiter.akutech-local.de>
     [not found]           ` <1024063905.30056@sj-nntpcache-5>
2002-06-15 14:13             ` Build Failure Richard Stallman

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