From: Andreas Schwab <schwab@linux-m68k.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Dan Nicolaescu <dann@gnu.org>, 5655@debbugs.gnu.org
Subject: bug#5655: incorrect paths for crt1.o, crtn.o, etc.
Date: Mon, 26 Apr 2010 19:33:39 +0200 [thread overview]
Message-ID: <m21ve25dak.fsf@igel.home> (raw)
In-Reply-To: <meljcaunuu.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 26 Apr 2010 13:26:17 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Andreas Schwab wrote:
>
>>> Sorry, I don't understand the proposal; but CRT_DIR == /usr/lib in the
>>> majority of cases. It can only be different on x86_64-*-linux-gnu* or
>>> s390x-*-linux-gnu* systems.
>>
>> Or sparc64-* or ppc64-*.
>
> How can CRT_DIR be different from /usr/lib on these systems, given the
> test of $canonical configure does?
Not CRT_DIR, but the location of crt0.o. Sorry for being unclear.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-04-26 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 4:30 bug#5655: 23.1; incorrect paths for crt1.o, crtn.o, etc Nathan Phillip Brink
2010-03-01 23:22 ` bug#5655: crt*.o Nathan Phillip Brink
2010-04-24 2:24 ` bug#5655: incorrect paths for crt1.o, crtn.o, etc Glenn Morris
2010-04-24 19:26 ` Dan Nicolaescu
2010-04-24 19:51 ` Glenn Morris
2010-04-25 21:19 ` Dan Nicolaescu
2010-04-26 16:36 ` Glenn Morris
2010-04-26 17:16 ` Andreas Schwab
2010-04-26 17:26 ` Glenn Morris
2010-04-26 17:33 ` Andreas Schwab [this message]
2010-04-26 17:33 ` Dan Nicolaescu
2010-04-27 3:18 ` Glenn Morris
2010-04-27 6:31 ` Sven Joachim
2010-04-27 6:51 ` Glenn Morris
2010-04-27 7:04 ` Glenn Morris
2010-04-27 7:11 ` Dan Nicolaescu
2010-04-27 7:49 ` Sven Joachim
2010-04-27 7:25 ` Sven Joachim
2010-04-27 17:33 ` Glenn Morris
2010-04-27 19:27 ` Sven Joachim
2010-04-27 19:32 ` Glenn Morris
2010-04-27 19:59 ` Sven Joachim
2010-04-27 20:17 ` Glenn Morris
2010-04-28 5:49 ` Sven Joachim
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=m21ve25dak.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=5655@debbugs.gnu.org \
--cc=dann@gnu.org \
--cc=rgm@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).