From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2)
Date: Wed, 14 May 2003 17:34:33 +0100 [thread overview]
Message-ID: <3EC27019.1060307@yahoo.co.uk> (raw)
In-Reply-To: <E19Fwc5-0008HD-00@fencepost.gnu.org>
Yes, it is a GNU/Linux system.
As it turns out, the solution (adding '-z nocombreloc' to LDFLAGS)
fixes problem with building current version of emacs as well.
It is a problem with 'combreloc' becoming the default since March 2002 in
GNU ld so it affects very new GNU/Linux system when trying to build
all versions of emacs and xemacs, in addition to very new GNU/Hurd systems,
and any other system for which GNU ld is the default linker and for which the
version of GNU ld is less than 14 months old.
I'll address cemacs/MULE separately.
Richard Stallman wrote:
> That's a somewhat time-wasting question - if I am on linux with
> gcc 3.2 glibc 2.3.x and Xfree 4.3.0 most certainly the linux
> distribution I use come with a more recent version of emacs or xemacs.
>
> If it contains those things, it appears to be a GNU/Linux
> distribution, not a distribution of Linux alone. See
> http://www.gnu.org/gnu/gnu-linux-faq.html.
>
> Now back to my question: why emacs 19.34 segfault when built against
> glibc-2.3 and Xfree 4.3.0?
>
> We're not maintaining Emacs 19.34 any more, because it is obsolete.
> Other people are free to work on it if they want to.
>
> In contrast,, we might be interested in trying to fix this problem
>
> I want to use a elisp script called cemacs (for Chinese inputs)
> but unfortunately the inclusion the MULE (Multi-lingual Extension)
> since version 20 has broken it.
>
> if you send a bug report with a precise complete test case.
>
> We are certainly interested in improving MULE. Could you write to
> emacs-devel@gnu.org and tell us why specifically MULE is not as good
> as cemacs for your usage?
>
next prev parent reply other threads:[~2003-05-14 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2003-05-12 16:12 ` emacs-19.34 segfaults when built with Xfree 4.3.0 (glibc2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 17:18 ` Thien-Thi Nguyen
2003-05-12 17:51 ` emacs-19.34 segfaults when built with Xfree 4.3.0(glibc2.3.x,gcc 3.2) Hin-Tak Leung
2003-05-12 18:15 ` Thien-Thi Nguyen
2003-05-12 19:00 ` Hin-Tak Leung
2003-05-12 20:36 ` Thien-Thi Nguyen
2003-05-12 22:11 ` Hin-Tak Leung
[not found] ` <mailman.6068.1052777215.21513.help-gnu-emacs@gnu.org>
2003-05-13 7:07 ` Kai Großjohann
[not found] ` <20030512164103.1607f814.samuel@ma.hw.ac.uk>
2003-05-12 16:25 ` emacs-19.34 segfauls when built with Xfree 4.3.0 (glibc 2.3.x,gcc 3.2) 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 [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-06 20:12 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=3EC27019.1060307@yahoo.co.uk \
--to=hintak_leung@yahoo.co.uk \
--cc=bug-gnu-emacs@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.
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).