From: Chong Yidong <cyd@stupidchicken.com>
Cc: HASHI Hiroaki <hashiz@tomba.meridiani.jp>
Subject: Re: emacs-current bootstrap fail on FreeBSD 6.2
Date: Mon, 09 Oct 2006 12:32:35 -0400 [thread overview]
Message-ID: <87iritbgbg.fsf@stupidchicken.com> (raw)
In-Reply-To: <87ac48xfeh.fsf@furball.mit.edu> (Chong Yidong's message of "Sat\, 07 Oct 2006 12\:24\:38 -0400")
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.pretest.bugs as well.
>> On emacs-current, make bootstrap stop fail.
>
> I can't reproduce this on GNU/Linux, and I don't know any Emacs
> developer who uses FreeBSD 6.2.
>
> Does this problem still occur with the latest CVS sources? If so, one
> way to narrow the problem down is to check out older sources (with
> CVS's "-D" flag), and see when it broke. Also, see if bootstrap works
> if you omit CFLAGS during configuration (though bootstrap works for me
> with those exact flags.)
>
>> How to repeat:
>> ----
>> % ./configure --with-gtk CFLAGS="-pipe -O2 -g"
>> % make bootstrap
>> .
>> Loading /home/hashiz/src/emacs/lisp/international/subst-big5.el (source)...
>> Loading /home/hashiz/src/emacs/lisp/international/subst-jis.el (source)...
>> Fatal error (11)Segmentation fault (core dumped)
>> *** Error code 1
Does this still happen with the latest CVS sources?
Does anyone on this list use FreeBSD 6.2, and is able to reproduce
this?
next parent reply other threads:[~2006-10-09 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061006.150001.39180026.hashiz@tomba.meridiani.jp>
[not found] ` <87ac48xfeh.fsf@furball.mit.edu>
2006-10-09 16:32 ` Chong Yidong [this message]
[not found] ` <20061010.021219.226799282.hashiz@tomba.meridiani.jp>
[not found] ` <87d591uypd.fsf@stupidchicken.com>
[not found] ` <20061010.145436.226789007.hashiz@tomba.meridiani.jp>
2006-10-10 14:39 ` emacs-current bootstrap fail on FreeBSD 6.2 Chong Yidong
2006-10-10 15:13 ` Andreas Schwab
2006-10-13 6:06 ` Stefan Monnier
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=87iritbgbg.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=hashiz@tomba.meridiani.jp \
/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.