From: Makoto Fujiwara <makoto@ki.nu>
To: emacs-devel@gnu.org
Subject: configure.in (START_FILES + LIB_STANDARD) and CRT_DIR sequence
Date: Sat, 24 Sep 2011 17:57:41 +0900 [thread overview]
Message-ID: <yfm7h4ys4fu.wl%makoto@ki.nu> (raw)
After following commit, with some Operating system, say NetBSD,
build fails to find _fini symbols.
-------------
2011-06-29 Glenn Morris <rgm@gnu.org>
* configure.in: Try to test for the required crt*.o files.
-------------
It turned out the testing line 1011 of below never get true
because CRT_DIR is empty yet. (Missing parenthesis is not important :-)
---------
t-105@makoto 17:49:33/110924(..work/emacs)% cat -n configure.in | sed -n 1002,1019p
1002 gnu-linux | gnu-kfreebsd )
1003 LIB_STANDARD='-lgcc -lc -lgcc $(CRT_DIR)/crtn.o'
1004 START_FILES='pre-crt0.o $(CRT_DIR)/crt1.o $(CRT_DIR)/crti.o'
1005 ;;
1006 hpux10-20 | hpux11 )
1007 LIB_STANDARD=-lc
1008 START_FILES='pre-crt0.o $(CRT_DIR)/crt0.o'
1009 ;;
1010 netbsd | openbsd )
1011 if test -f $CRT_DIR/crti.o; then
1012 LIB_STANDARD='-lgcc -lc -lgcc $(CRT_DIR)/crtend.o $(CRT_DIR)/crtn.o'
1013 START_FILES='pre-crt0.o $(CRT_DIR)/crt0.o $(CRT_DIR)/crti.o $(CRT_DIR)/crtbegin.o'
1014 else
1015 LIB_STANDARD='-lgcc -lc -lgcc $(CRT_DIR)/crtend.o'
1016 START_FILES='pre-crt0.o $(CRT_DIR)/crt0.o $(CRT_DIR)/crtbegin.o'
1017 fi
1018 ;;
1019 esac
t-105@makoto 17:49:38/110924(..work/emacs)%
---------
I think the order of
START_FILES + LIB_STANDARD
and
CRT_DIR handling of configure.in
should be swapped. Say CRT_DIR comes before
START_FILES processing.
Am I right ?
Thanks always,
---
Makoto Fujiwara,
Chiba, Japan, Narita Airport and Disneyland prefecture.
next reply other threads:[~2011-09-24 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 8:57 Makoto Fujiwara [this message]
2011-09-24 9:41 ` configure.in (START_FILES + LIB_STANDARD) and CRT_DIR sequence Makoto Fujiwara
2011-09-24 10:56 ` Makoto Fujiwara
2011-09-24 19:09 ` 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=yfm7h4ys4fu.wl%makoto@ki.nu \
--to=makoto@ki.nu \
--cc=emacs-devel@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).