From: Ryan Yeske <rcyeske@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: 22.0.98 build problem
Date: Thu, 26 Apr 2007 02:01:43 -0700 (PDT) [thread overview]
Message-ID: <20070426090143.95CA2142E4@owie.localdomain> (raw)
In-Reply-To: <hx1wi7vbn2.fsf@fencepost.gnu.org>
I ran "configure --build=powerpc-unknown-openbsd4.0", which is
probably not a totally faithful simulation of what you are doing, but
configure correctly picked up the definition of LINKER from s/netbsd.h
and used this to set LD=$(CC) -nostartfiles in src/Makefile.in. This
is apparently equivalent to -nostdlib on your platform. So the
relevant question might be, why did this not happen for you?
Maybe the code in m/macppc.h:
#if defined(__OpenBSD__)
#define ORDINARY_LINK
#endif
defines ORDINARY_LINK, which looks like it would cause Makefile.in to
set LD = $(CC).
This could all be total junk, so don't invest too much time on the
basis of this. Does it work if you delete those lines from macppc.h?
Up to 7 years ago (!) ORDINARY_LINK was also defined for NetBSD. Maybe
it should no longer be defined on OpenBSD either. Hand-wave,
hand-wave.
Thanks for the useful pointers here. Yes, when I remove those lines
it does link. Here is exactly what I did:
*** macppc.h 02 Mar 2007 16:02:17 -0800 1.15
--- macppc.h 26 Apr 2007 01:07:18 -0700
***************
*** 66,75 ****
/* #define NO_SOCK_SIGIO */
- #if defined(__OpenBSD__)
- #define ORDINARY_LINK
- #endif
-
#define UNEXEC unexelf.o
#define NO_TERMIO
--- 66,71 ----
Unfortunatly, I get a segfault in the next step. Any idea how to go
about debugging this issue?
./temacs --batch --load loadup bootstrap
Loading loadup.el (source)...
Using load-path (/home/rcyeske/emacs/lisp /home/rcyeske/emacs/lisp/emacs-lisp /home/rcyeske/emacs/lisp/language /home/rcyeske/emacs/lisp/international /home/rcyeske/emacs/lisp/textmodes)
Loading emacs-lisp/byte-run (source)...
Loading emacs-lisp/backquote (source)...
Loading subr (source)...
Loading version.el (source)...
Loading widget (source)...
Loading custom (source)...
Loading emacs-lisp/map-ynp (source)...
Loading env (source)...
Loading cus-start (source)...
Loading international/mule (source)...
Loading international/mule-conf.el (source)...
Loading format (source)...
Loading bindings (source)...
Loading /home/rcyeske/emacs/lisp/files.el (source)...
*** Signal 11
Stop in /home/rcyeske/emacs/src (line 270 of Makefile).
*** Error code 1
Stop in /home/rcyeske/emacs (line 792 of Makefile).
*** Error code 1
Stop in /home/rcyeske/emacs (line 786 of Makefile).
Compilation exited abnormally with code 1 at Thu Apr 26 01:05:18
next prev parent reply other threads:[~2007-04-26 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 19:19 22.0.98 build problem Ryan Yeske
2007-04-23 19:40 ` Alfred M. Szmidt
2007-04-23 21:14 ` Ryan Yeske
2007-04-24 16:03 ` Richard Stallman
2007-04-26 4:16 ` Ryan Yeske
2007-04-26 7:27 ` Glenn Morris
2007-04-26 9:01 ` Ryan Yeske [this message]
2007-04-28 4:41 ` 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=20070426090143.95CA2142E4@owie.localdomain \
--to=rcyeske@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=rms@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).