From: Glenn Morris <rgm@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 5655@debbugs.gnu.org
Subject: bug#5655: incorrect paths for crt1.o, crtn.o, etc.
Date: Mon, 26 Apr 2010 12:36:34 -0400 [thread overview]
Message-ID: <v1sk6iuq5p.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20100228043052.5378236D56@ohnopublishing.net>
Dan Nicolaescu wrote:
> One more thing: can src/s/gnu-linux.h be changed to use $(CRT_DIR),
> that would avoid the need to special case GNU_LINUX in the src/m/* files...
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. So you should feel free to replace
/usr/lib by $CRT_DIR anywhere else basically.
It would be nice to move all the crt*.o logic entirely to configure
(and so make the --with-crt-dir option work the same on all
platforms), but I don't know how to replicate the logic of m/sparc.h
and m/macppc.h in configure.in.
next prev parent reply other threads:[~2010-04-26 16:36 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 [this message]
2010-04-26 17:16 ` Andreas Schwab
2010-04-26 17:26 ` Glenn Morris
2010-04-26 17:33 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v1sk6iuq5p.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=5655@debbugs.gnu.org \
--cc=dann@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.