unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: David Kastrup <dak@gnu.org>
Cc: bzg@altern.org, 17215@debbugs.gnu.org
Subject: bug#17215: Build failure
Date: Wed, 09 Apr 2014 12:19:26 +0200	[thread overview]
Message-ID: <87mwfurej5.fsf@yahoo.fr> (raw)
In-Reply-To: <87k3b0giip.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 08 Apr 2014 13:36:30 +0200")

[I'm cc-ing Bastien because he had a similar problem IIRC]

Hi David,

> Still dumps core.  Looks pretty much the same to me:
> #0  0x40022424 in __kernel_vsyscall ()
> #1  0x416b60c6 in raise (sig=sig@entry=6)
>     at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37

You could try Daniel's suggestion to bug#17184, i.e. compile with
-DSYSTEM_PURESIZE_EXTRA=10000000

Perhaps it is time to increase BASE_PURESIZE ? FWIW I applied this patch
to my local branch :

	Modified   src/ChangeLog
diff --git a/src/ChangeLog b/src/ChangeLog
index 2b00e60..9d0d8f0 100644
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -1,3 +1,7 @@
+2014-04-09  Nicolas Richard  <theonewiththeevillook@yahoo.fr>
+
+	* puresize.h (BASE_PURESIZE): Increase to 1720000.
+
 2014-04-09  Stefan Monnier  <monnier@iro.umontreal.ca>
 
 	* insdel.c (prepare_to_modify_buffer_1): Cancel lock-file checks and
	Modified   src/puresize.h
diff --git a/src/puresize.h b/src/puresize.h
index 0ee29d8..ad591c7 100644
--- a/src/puresize.h
+++ b/src/puresize.h
@@ -40,7 +40,7 @@ along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.  */
 #endif
 
 #ifndef BASE_PURESIZE
-#define BASE_PURESIZE (1700000 + SYSTEM_PURESIZE_EXTRA + SITELOAD_PURESIZE_EXTRA)
+#define BASE_PURESIZE (1720000 + SYSTEM_PURESIZE_EXTRA + SITELOAD_PURESIZE_EXTRA)
 #endif
 
 /* Increase BASE_PURESIZE by a ratio depending on the machine's word size.  */

-- 
Nico.





  reply	other threads:[~2014-04-09 10:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  8:08 bug#17215: Build failure David Kastrup
2014-04-07 20:47 ` Glenn Morris
2014-04-08 10:42   ` David Kastrup
2014-04-08 10:50     ` Daniel Colascione
2014-04-08 11:36       ` David Kastrup
2014-04-09 10:19         ` Nicolas Richard [this message]
2014-04-09 10:48           ` Daniel Colascione
2014-04-09 12:43             ` Stefan Monnier
2014-04-09 15:38           ` Bastien
     [not found] ` <handler.17215.B.139685811224063.ack@debbugs.gnu.org>
2014-04-11 15:51   ` bug#17215: Acknowledgement (Build failure) David Kastrup
2014-04-11 19:11     ` Daniel Colascione
2014-04-11 20:10       ` Eli Zaretskii
2014-04-11 20:18         ` Stefan Monnier
2014-04-11 20:11       ` Stefan Monnier
2014-04-11 20:58         ` David Kastrup
2014-04-11 21:34           ` Daniel Colascione
2014-04-12 13:19             ` Stefan Monnier
2014-04-12  8:35         ` Eli Zaretskii
2014-04-12 13:21           ` Stefan Monnier
2014-04-12 14:18             ` 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=87mwfurej5.fsf@yahoo.fr \
    --to=theonewiththeevillook@yahoo.fr \
    --cc=17215@debbugs.gnu.org \
    --cc=bzg@altern.org \
    --cc=dak@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).