From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 13528@debbugs.gnu.org
Subject: bug#13528: "find_emacs_zone_regions: too many regions" --with-wide-int on PPC 7447A Mac OS X 10.5.8
Date: Fri, 25 Jan 2013 17:45:32 +0100 [thread overview]
Message-ID: <F1E40C1A-DAB0-4FF3-8E1F-DB1EC6544CD8@Freenet.DE> (raw)
In-Reply-To: <20D89A68-7416-46E1-974F-48C891937B2A@Freenet.DE>
Am 22.01.2013 um 23:29 schrieb Peter Dyballa:
> I did not try that patch yet – because I was compiling GNU Emacs
> from the same code basis as yesterday, now without the bootstrap
> option. And it builds with -Os, and if fails when building the
> bootstrap targets with -Os!
I have indeed undone all patches to src/unexmacosx.c. Within the
clearly set build environments for configure, make, make install GNU
Emacs builds without problems. I updated the sources and still no
problem. The real problem is that 'make bootstrap' does not honour the
previous configure step and tries something that is bound to fail. If
this behaviour continues, the sequence of make distclean, configure,
make, make install seems to be a valid work-around.
My bug report was wrong: I did not see what 'make bootstrap' was
really performing.
--
Greetings
Pete
The human brain operates at only 10% of its capacity. The rest is
overhead for the operating system.
next prev parent reply other threads:[~2013-01-25 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 22:19 bug#13528: 24.3.50; "find_emacs_zone_regions: too many regions" --with-wide-int on PPC 7447A Mac OS X 10.5.8 Peter Dyballa
2013-01-22 20:46 ` bug#13528: " Paul Eggert
2013-01-22 22:29 ` Peter Dyballa
2013-01-22 22:37 ` Paul Eggert
2013-01-22 23:11 ` Peter Dyballa
2013-01-24 21:01 ` Peter Dyballa
2013-01-25 16:45 ` Peter Dyballa [this message]
2013-02-08 16:25 ` Paul Eggert
2013-01-22 23:35 ` Peter Dyballa
2013-01-23 1:57 ` Paul Eggert
2013-01-23 10:40 ` Peter Dyballa
2013-01-23 23:37 ` 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=F1E40C1A-DAB0-4FF3-8E1F-DB1EC6544CD8@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=13528@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.