From: Daniel Brooks <db48x@yahoo.com>
Subject: Re: emacs crashes during make bootstrap
Date: Sun, 10 Dec 2006 01:45:02 -0600 [thread overview]
Message-ID: <m3zm9wmby9.fsf@db48x.waldenweb.com> (raw)
In-Reply-To: mailman.1703.1165703878.2155.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 09.12.2006 um 21:42 schrieb Daniel Brooks:
>
>> I've successfully built emacs 22 from cvs on this machine
>
> What machine is this? Which operating system? Is your compiler 64 bit
> fit? Do you use flags to create a 64 application? Are your libraries
> 64 bit ready? Can you try to compile with -O0 among the CFLAGS?
>
Fedora Core 5, 64 bit compiler, I used whatever flags configure thought best. However, just for laughs, I nuked my emacs directory and grabbed a fresh copy from cvs, and it built perfectly the first time. I guess make distclean didn't do the job well enough. Thanks though :)
db48x
prev parent reply other threads:[~2006-12-10 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 20:42 emacs crashes during make bootstrap Daniel Brooks
2006-12-09 22:37 ` Peter Dyballa
[not found] ` <mailman.1703.1165703878.2155.help-gnu-emacs@gnu.org>
2006-12-10 7:45 ` Daniel Brooks [this message]
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=m3zm9wmby9.fsf@db48x.waldenweb.com \
--to=db48x@yahoo.com \
/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.
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).