From: "Mandalemula, Rajesh" <Rajesh.Mandalemula@deshaw.com>
To: "4559@debbugs.gnu.org" <4559@debbugs.gnu.org>
Subject: bug#4559: temacs core dump when compiling emacs under solaris
Date: Mon, 13 Sep 2010 15:53:51 +0530 [thread overview]
Message-ID: <6404320ADBB23E4BAB6DBFEB925CFFCD2796CE77B6@HYDMBX2.winmail.deshaw.com> (raw)
In-Reply-To: <4ABD8AAD.9010400@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Hi,
I faced the same issue on Solaris 10 x86 while building a 64-bit emacs. Eventually, it turned out to be a wrong build host (guessed by config.guess) causing the segfault.
<<<< from config.guess >>>>
i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*)
eval $set_cc_for_build
SUN_ARCH="i386"
# If there is a compiler, see if it is configured for 64-bit objects.
# Note that the Sun cc does not turn __LP64__ into 1 like gcc does.
# This test works for both compilers.
if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | \
(CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
SUN_ARCH="x86_64"
fi
fi
echo ${SUN_ARCH}-pc-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
<<<< from config.guess >>>>
config.guess sets SUN_ARCH to 'x86_64' only if preprocessor defines '__amd64' - however, the config.guess script does not use the CFLAGS passed (which actually sets -m64) for this preprocessor check and hence the build host is not set correctly.
Passing an explicit "--build=x86_64-pc-solaris2.10" to the configure script or setting CC="<compiler> -m64" solves the issue.
Hope this helps.
Thanks. Rajesh
[-- Attachment #2: Type: text/html, Size: 4041 bytes --]
next prev parent reply other threads:[~2010-09-13 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 3:29 bug#4559: temacs core dump when compiling emacs under solaris snnn
2010-09-13 10:23 ` Mandalemula, Rajesh [this message]
2010-09-13 14:47 ` Andreas Schwab
2010-09-14 4:28 ` Kevin Rodgers
2010-09-14 8:02 ` Andreas Schwab
2011-10-06 6:55 ` Glenn Morris
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=6404320ADBB23E4BAB6DBFEB925CFFCD2796CE77B6@HYDMBX2.winmail.deshaw.com \
--to=rajesh.mandalemula@deshaw.com \
--cc=4559@debbugs.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 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).