From: Paul Eggert <eggert@cs.ucla.edu>
To: hua-jian.luo@oracle.com
Cc: 14407@debbugs.gnu.org
Subject: bug#14407: Can't compile emacs trunk on Solaris 11
Date: Thu, 16 May 2013 20:59:05 -0700 [thread overview]
Message-ID: <5195AB09.4030909@cs.ucla.edu> (raw)
In-Reply-To: <wotghai3s59k.fsf@oracle.com>
I tried to reproduce the problem on Solaris 10 sparc as well,
and can't do it. I also tried building 32-bit Emacs
implementations, using "gcc -m32", and couldn't reproduce
the problem there either.
I did notice serious problems in your build log
<http://debbugs.gnu.org/cgi/bugreport.cgi?msg=5;filename=compile-emacs-log.gz;att=1;bug=14407>;
pkg-config is repeatedly dumping core. For example:
checking for alsa >= 1.0.0... ./configure: line 8975: 906 Killed "$PKG_CONFIG" --exists "$ALSA_MODULES" 2>&5
no
So my guess is that /opt/csw is part of the problem.
I suggest that you build without using /opt/csw, by
removing it from your PATH, and then rebuilding from
scratch.
>> Which is the most-recent trunk bzr version that worked for you?
>> You can bisect to find that.
>
> A long time ago, but the release can work with --without-all
The idea of bisecting is that you can use binary search to
find out the exact revision number that stopped working
for you. It takes a bit of time, but it can be well worth
doing.
> And how can I compile a debugable emacs that I can use mdb/gdb to look
> into it?
That should happen by default. Just type "./configure; make"
in a fresh copy. Make sure /opt/csw is not mentioned in your
environment, though: "printenv | grep /opt/csw" should output nothing.
next prev parent reply other threads:[~2013-05-17 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 6:04 bug#14407: Can't compile emacs trunk on Solaris 11 Huajian Luo
2013-05-15 7:52 ` Paul Eggert
2013-05-16 8:22 ` Huajian Luo
2013-05-17 3:59 ` Paul Eggert [this message]
2013-05-17 8:23 ` Huajian Luo
2013-05-17 21:32 ` Paul Eggert
2013-05-18 6:06 ` Huajian Luo
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=5195AB09.4030909@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=14407@debbugs.gnu.org \
--cc=hua-jian.luo@oracle.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).