public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kean Johnston <jkj@sco.com>
To: gcc@gcc.gnu.org
Subject: What's the best way of including extra files for gcc lib dir?
Date: Sun, 17 Jul 2005 23:27:00 -0000	[thread overview]
Message-ID: <42DAE93A.3080807@sco.com> (raw)

Hi All,

What is the best way of including target-specific files in the
version-specific gcc library directory? I need to include a
file that will be referenced from LINK_SPEC as "gcc.map%s".
IE, in the same place the startup files are located. So
really I need to know two things:
1) How to I persuade the GCC makefile to install it, and
2) Whats the best place to put it in the source tree?

Bear inmind this must be available during bootstrapping too.

I suspect it may require additions to "extra_parts" in config.gcc,
and then suitable rules for creating it in the t-* fragment.
Is this correct? Is it acceptable for that t-* fragment to
do something like:

gcc.map: $(srcdir)/config/i386/gcc.map
   -rm -f gcc.map
   -cp -f $(srcdir)/config/i386/gcc.map $@

Any help / advice would be greatly appreciated.

Kean

             reply	other threads:[~2005-07-17 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 23:27 Kean Johnston [this message]
2005-07-18  5:45 ` Ian Lance Taylor

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=42DAE93A.3080807@sco.com \
    --to=jkj@sco.com \
    --cc=gcc@gcc.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. 
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).