From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Subject: emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x, gcc 3.2)
Date: Tue, 06 May 2003 21:12:05 +0100 [thread overview]
Message-ID: <3EB81715.10902@yahoo.co.uk> (raw)
I am trying to build emacs-19.34 against glibc-2.3 and Xfree 4.3.0
on linux with gcc 3.2. The binary works with -nw switch, but
when I run it without -nw, it segfaults with Fatal Error(11).
So it seems to be an X-related problem.
I had an older binary which was compiled by gcc 2.95.x against
Xfree 4.1(?) and glibc-2.1 (maybe 2.0?) which still works on
this current system.
#uname -a
Linux pc7221 2.4.20 #2 Wed Apr 23 08:44:11 BST 2003 i686 unknown
#cat /var/log/XFree86.log
XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20 i686 [ELF]
# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/specs
Configured with: ../gcc-3.2.2/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld
--verbose --target=i386-slackware-linux --host=i386-slackware-linux
Thread model: posix
gcc version 3.2.2
next reply other threads:[~2003-05-06 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 20:12 Hin-Tak Leung [this message]
[not found] <mailman.5658.1052251660.21513.help-gnu-emacs@gnu.org>
2003-05-07 2:01 ` emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x, gcc 3.2) Sam Halliday
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 14:40 emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 15:22 ` Thien-Thi Nguyen
[not found] ` <20030512164103.1607f814.samuel@ma.hw.ac.uk>
2003-05-12 16:25 ` Hin-Tak Leung
[not found] ` <20030512180149.371bb9d5.samuel@ma.hw.ac.uk>
2003-05-12 17:29 ` Hin-Tak Leung
2003-05-12 22:41 ` Sam Halliday
2003-05-12 22:52 ` Hin-Tak Leung
2003-05-14 2:51 ` Eli Zaretskii
2003-05-14 13:48 ` Richard Stallman
2003-05-14 16:34 ` Hin-Tak Leung
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=3EB81715.10902@yahoo.co.uk \
--to=hintak_leung@yahoo.co.uk \
/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).