unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap failure using 'make -j4' [Cygwin]
Date: Sat, 22 May 2010 00:45:31 +0200	[thread overview]
Message-ID: <4BF70D0B.9050106@alice.it> (raw)
In-Reply-To: <83r5l5yw33.fsf@gnu.org>

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

Il 21/05/2010 19.59, Eli Zaretskii ha scritto:
>> Date: Fri, 21 May 2010 18:57:41 +0200
>> From: Angelo Graziosi<>
>> Cc:
>>
>> In the build log there is *not* track of the command to compile
>> dispnew.c: as you see 'grep' finds only
>>
>> make[2]: *** [dispnew.o] Error 1
>
> I cannot reproduce this on GNU/Linux with "make -j4 bootstrap".

Indeed. It bootstraps fine on GNU/Linux Kubuntu 10.04

> How many CPU cores do you have on that machine?

It is an AMD Athlon 64 X2 Dual Core Processor 3800+ 2.03 GHz, 1.75GB RAM

> If nothing else gives a clue, post the entire transcript of the
> "configure" and "make -j4 bootstrap" steps.

For completeness I have attached the full build log (40K, 8K compressed).

With 'make -j4 -d 2>&1 | tee foo', as you suggested, I cannot reproduce 
the problem: it seems to bootstrap completely (at least emacs.exe is 
built and dispnew.c compiled).

My build script use

${source_dir}/configure --prefix=${prefix_dir}
make -j4 bootstrap


Ciao,
Angelo.

[-- Attachment #2: build-emacs-gtk-24.0.50-r100410.log.bz2 --]
[-- Type: application/octet-stream, Size: 7901 bytes --]

  parent reply	other threads:[~2010-05-21 22:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 14:53 Bootstrap failure using 'make -j4' [Cygwin] Angelo Graziosi
2010-05-21 16:16 ` Eli Zaretskii
2010-05-21 16:57   ` Angelo Graziosi
2010-05-21 17:43     ` Eli Zaretskii
2010-05-21 17:59     ` Eli Zaretskii
2010-05-21 18:45       ` Eli Zaretskii
2010-05-21 22:45       ` Angelo Graziosi [this message]
2010-05-22  6:57         ` Eli Zaretskii
2010-05-22  7:16           ` Glenn Morris
2010-05-22  7:29             ` Glenn Morris
2010-05-22  8:19             ` Eli Zaretskii
2010-05-22 11:20               ` Andreas Schwab
2010-05-22 12:53                 ` Eli Zaretskii
2010-05-22 11:00           ` Jan Djärv
2010-05-22 12:46             ` Eli Zaretskii
2010-05-22 13:00               ` Jan Djärv
2010-05-22 13:06                 ` David Engster
2010-05-22 13:45                   ` Jan Djärv
2010-05-22 13:21                 ` Eli Zaretskii
2010-05-22 13:41                   ` David Engster
2010-05-22 14:00                     ` Jan Djärv
2010-05-22 13:54                   ` Jan Djärv
2010-05-22 14:10                     ` Eli Zaretskii
2010-05-22 13:35           ` Angelo Graziosi
2010-05-22 14:08             ` Eli Zaretskii
2010-05-23 11:51           ` Angelo Graziosi
2010-05-23 17:12             ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=4BF70D0B.9050106@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --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 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).