This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: i386-pc-solaris2.5.1: recent snapshots can't build emacs-20.2
- To: law at cygnus dot com
- Subject: Re: i386-pc-solaris2.5.1: recent snapshots can't build emacs-20.2
- From: Jim Meyering <meyering at ascend dot com>
- Date: 17 Aug 1998 14:45:08 -0500
- Cc: egcs at cygnus dot com, rms at gnu dot org
- References: <11921.903381880@hurl.cygnus.com>
| In message <87iujrs9ax.fsf@ascend.com>you write:
| > | OK. This has nothing to do with whatever cvs version we're running. It
| > | sounds more like the typical development instability. What happens if
| > | you try to build something newer, paricularly off the egcs-1.1 branch?
| >
| > I've been doing that (with the trunk, then, since the branch, with 1.1)
| > for more than a month. It works fine. Of course, using the resulting
| > compiler to try to build emacs is what fails.
| I'm really confused -- look back at what you said a little while ago:
|
| | > | In message <873eawf8n0.fsf@ascend.com>you write:
| | > | > I did try to build a few `cvs update -D DATE'-selected
| | > | > versions of egcs, but none of them bootstrapped. What version
| | > | > of CVS is running on Cygnus' egcs repository?
|
| So in fact, you can bootstrap, but we still have problems with XEmacs right?
*X*Emacs? could you be thinking of something different? I saw a thread
about an abort with XEmacs. This is a segfault that happens during the
make process for *FSF* emacs-20.2 (and 20.2.99) when the just-created
emacs executable is run like this:
../src/emacs -batch --no-init-file --no-site-file --multibyte ...
I bootstrapped the head of egcs-1.1 after the last change and installed it.
I cannot build a working FSF emacs 20.2 using that compiler.
Reading specs from \
/p/p/egcs-980817-00h35/lib/gcc-lib/i386-pc-solaris2.5.1/egcs-2.91.54/specs
gcc version egcs-2.91.54 19980816 (gcc2 ss-980609 experimental)
Note that compiling and linking go just fine.
David Miller hypothesized that the failure is related to the unexec.