From: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
To: 10896@debbugs.gnu.org
Cc: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
Subject: bug#10896: Suggested Fix (for configure)
Date: Tue, 28 Feb 2012 02:19:33 +0900 [thread overview]
Message-ID: <4F4BBB25.8030007@yk.rim.or.jp> (raw)
In-Reply-To: <4F4B86C4.8030101@yk.rim.or.jp>
OK, this is a problem in the next major release of Debian.
I found out that this choice of using //usr/lib/i386-linux-gnu/ to store
crt1.o and friends are necessitated by the Debian's choice of
multi-arch support in one way or the other.
So Debian, starting the next major revision called Wheezy (or whatever),
will store crt1.o not under /usr/lib directly and elsewhere (under a
subdirectory of /usr/lib based on architecture name, it seems.)
It turns out in the current major release, crt1.o *IS* stored under
/usr/lib. That is why I could compile emacs-23.3 May 2011 without
--with-crt-dir.
Upstream Debian package maintainers are advised to face this issue:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libc6-dev;dist=unstable
I have no idea how wide the problem will be.
But maybe as a protective measure, emacs configure can be patched to
test CRT_DIR validity like the one I mentioned as a patch to catch this
type of configuration errors in advance.
Anyway, the lack of checking *OUTSIDE* and *AFTER* CRT_DIR is set is an
obvious error and so the checking should be done after the CRT_DIR
variable is set outside case like I reported IMHO.
This should help us catch other strange runtime library layout.
TIA
next prev parent reply other threads:[~2012-02-27 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 3:04 bug#10896: 23.4; --with-crt-dir was required since crt1.0 not found (on *32bit* system) ishikawa
2012-02-27 13:36 ` bug#10896: Suggested Fix (for configure) ISHIKAWA,chiaki
2012-02-27 17:19 ` ISHIKAWA,chiaki [this message]
2012-02-27 19:25 ` bug#10896: 23.4; --with-crt-dir was required since crt1.0 not found (on *32bit* system) Glenn Morris
2012-02-27 19:39 ` Glenn Morris
2012-02-28 12:33 ` ISHIKAWA,chiaki
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=4F4BBB25.8030007@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--cc=10896@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).