From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 12126@debbugs.gnu.org
Subject: bug#12126: 24.1.50; compilation --with-wide-int on PowerPC 32-bit leads to: Maximum buffer size exceeded
Date: Sat, 4 Aug 2012 18:10:38 +0200 [thread overview]
Message-ID: <539ED040-9637-497E-A191-C4CE4CFB0196@Freenet.DE> (raw)
In-Reply-To: <B08028E2-7E73-405B-9B70-30D7BFDA1EEA@swipnet.se>
Am 03.08.2012 um 18:31 schrieb Jan Djärv:
> Does it work if you just
> % configure --with-ns
Yes, compilation finishes then. It makes no difference whether I use
MacPorts or Fink and whether the compiler is
• powerpc-apple-darwin9-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple
Inc. build 5555) (LLVM build 2064.3)
• powerpc-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5577)
• powerpc-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5493)
My test started with that simple configure line and MacPorts and then
a 'make bootstrap'. This took hours, followed by 'make install'. The
next step was a new configuration followed by make and 'make install',
taking approximately 20-25 min. So I produced six versions of
Emacs.app. None really worked. When I launched them with open they
crashed at some time when initialising/executing my init file and re-
establishing previous session and desktop. When I invoked the Emacs
binary inside the application bundle with '--debug-init -Q' and I
invoked dired with C-x d and accepted the root of the GNU Emacs'
sources as directory with RET the NS variant instantly crashed.
--
Greetings
Pete
Encryption, n.:
A powerful algorithmic encoding technique employed in the creation of
computer manuals.
next prev parent reply other threads:[~2012-08-04 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 21:41 bug#12126: 24.1.50; compilation --with-wide-int on PowerPC 32-bit leads to: Maximum buffer size exceeded Peter Dyballa
2012-08-03 16:31 ` Jan Djärv
2012-08-04 16:10 ` Peter Dyballa [this message]
2012-08-04 20:54 ` Peter Dyballa
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=539ED040-9637-497E-A191-C4CE4CFB0196@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=12126@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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.