From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Emacs CVS Crash
Date: Wed, 7 Sep 2005 11:13:51 +1200 [thread overview]
Message-ID: <17182.8879.146245.74953@farnswood.snap.net.nz> (raw)
In-Reply-To: <431E1088.2000803@ig.com.br>
That looks like gcc thats crashed not Emacs. If its a bug with gcc, should
you be reporting it to them?
Nick
Vinicius Jose Latorre writes:
> Hi Folks,
>
>
> I've just updated Emacs sources from CVS today.
>
> Then:
>
> $ make maintainer-clean
> $ ./configure --prefix=/home/download/emacs
> $ make bootstrap
> [...skipped for brevity...]
> gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -DUSE_LUCID -I.
> -I/home/vinicius/work/emacs/src -D_BSD_SOURCE -I/usr/X11R6/include -g
> -O2 indent.c
> gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -DUSE_LUCID -I.
> -I/home/vinicius/work/emacs/src -D_BSD_SOURCE -I/usr/X11R6/include -g
> -O2 search.c
> search.c: In function `Fset_match_data':
> search.c:2974: internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
> make[2]: *** [search.o] Error 1
> make[2]: Leaving directory `/home/vinicius/work/emacs/src'
> make[1]: *** [src] Error 2
> make[1]: Leaving directory `/home/vinicius/work/emacs'
> make: *** [bootstrap-build] Error 2
>
>
> Vinicius
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2005-09-06 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 21:56 Emacs CVS Crash Vinicius Jose Latorre
2005-09-06 23:07 ` Kim F. Storm
2005-09-06 23:13 ` Nick Roberts [this message]
2005-09-07 3:31 ` Vinicius Jose Latorre
2005-09-07 10:01 ` Richard M. Stallman
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=17182.8879.146245.74953@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
/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.