From: Eli Zaretskii <eliz@gnu.org>
To: Eric LeBlanc <cognefou@hotmail.com>
Cc: 25141@debbugs.gnu.org
Subject: bug#25141: Compilation issue on AIX 7.1 and 64 bits
Date: Sat, 02 Sep 2017 15:11:43 +0300 [thread overview]
Message-ID: <831snp1erk.fsf@gnu.org> (raw)
In-Reply-To: <YQXPR01MB0197A7E922D98266057C8086D3970@YQXPR01MB0197.CANPRD01.PROD.OUTLOOK.COM> (message from Eric LeBlanc on Sun, 25 Dec 2016 14:42:41 +0000)
unblock 24655 by 25141
thanks
> From: Eric LeBlanc <cognefou@hotmail.com>
> Date: Sun, 25 Dec 2016 14:42:41 +0000
> Cc: "25141@debbugs.gnu.org" <25141@debbugs.gnu.org>
>
> Probably, but I won't count too much on 32 bits binary because we tried two RPM emacs packages, one from
> IBM website and the other from BULLFREEWARE website and they both ended with a "Segmentation Fault"
> with a core dump when we execute "emacs".
>
> I also played with LDR_CNTRL variable without any success.
>
> It seems that AIX 7.1 is very memory strict with 32 bits binaries and I'm sure that "unexec" is doing some
> memory dump to the final emacs binary that AIX 7.1 doesn't like.
>
> That's why I'm tyring to compile in 64 bits.
>
> For the moment, "temacs" in 64 bits works well but slow to start. I'm stuck at 'unexaix' operation and I'm not
> an expert in XCOFF binary file. I know that 'unexaix.c' isn't adapted for 64 bits binaries and I tried to make
> some modifications as I wrote earlier by enabling __XCOFF64__ in "unexaix.c" source code, without success
> since it generates a huge 4GB emacs binary, but I know I'm not so far to fix it.
Without any additional comments during the last 8 months, and AIX
being a platform of secondary importance, I don't see why this bug
should block the release of Emacs 26.1.
If you have any news on these issues, please tell.
Thanks.
next prev parent reply other threads:[~2017-09-02 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 18:20 bug#25141: Compilation issue on AIX 7.1 and 64 bits Eric LeBlanc
2016-12-08 20:48 ` Eric LeBlanc
2016-12-23 20:27 ` Eli Zaretskii
2016-12-24 14:05 ` Eric LeBlanc
2016-12-24 16:11 ` Eli Zaretskii
2016-12-25 14:42 ` Eric LeBlanc
2017-09-02 12:11 ` Eli Zaretskii [this message]
2016-12-25 7:31 ` Paul Eggert
2020-08-12 0:25 ` Stefan Kangas
2020-08-12 1:17 ` Paul Eggert
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=831snp1erk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25141@debbugs.gnu.org \
--cc=cognefou@hotmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).