From: Andreas Schwab <schwab@suse.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: where to report bootstrap bugs?
Date: Wed, 02 Jan 2008 14:52:14 +0100 [thread overview]
Message-ID: <je7iis5o8h.fsf@sykes.suse.de> (raw)
In-Reply-To: <864pdwuzgm.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed\, 02 Jan 2008 07\:30\:33 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Ah, thanks for the hint! I looked through my CFLAGS and found that the
> bug happens with CFLAGS '-malign-double'
-malign-double changes the ABI.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-01-02 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:35 GNU/Linux (Ubuntu 7.10) bootstrap from a CVS checkout fails ("Maximum buffer size exceeded") Ted Zlatanov
2007-11-30 23:17 ` Ted Zlatanov
2007-12-14 20:52 ` make bootstrap fails from fresh CVS checkout (was: GNU/Linux (Ubuntu 7.10) bootstrap from a CVS checkout fails ("Maximum buffer size exceeded")) Ted Zlatanov
2007-12-31 18:17 ` where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout) Ted Zlatanov
2007-12-31 20:45 ` Eli Zaretskii
2007-12-31 21:14 ` where to report bootstrap bugs? Michael Albinus
2007-12-31 21:29 ` Ted Zlatanov
2007-12-31 22:15 ` Dan Nicolaescu
2008-01-02 13:30 ` Ted Zlatanov
2008-01-02 13:52 ` Andreas Schwab [this message]
2008-01-02 16:42 ` Ted Zlatanov
2008-01-02 17:42 ` Dan Nicolaescu
2008-01-01 3:18 ` where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout) Richard Stallman
2007-12-31 20:57 ` repost of 'make bootstrap' problem " Ted Zlatanov
2008-01-01 1:30 ` repost of 'make bootstrap' problem Thien-Thi Nguyen
2008-01-01 19:48 ` Ted Zlatanov
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=je7iis5o8h.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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.
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.