linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Paolo Scaffardi <arsenio@tin.it>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: HARDHAT: hhl-relocation... how to use it?
Date: Tue, 05 Sep 2000 10:14:33 -0700	[thread overview]
Message-ID: <39B529F9.654F7A88@mvista.com> (raw)
In-Reply-To: 006d01c0171a$66f9a840$0a00010a@paoloweb


The hhl-relocation program is a wrapper which is used for relocation
gcc.

GCC has many hard coded paths in it.  We have a system to bypass those
hard coded paths using environment variables.  During the RPM install,
if you chose to install other then the default prefix (if do an rpm -qip
gcc* you'll see it is relocatable) a small script is run to adjust the
default prefix inside of hhl-relocation, and then rename all of the gcc
executables (gcc, g++, etc) to *.real.  It then sets up a sym link from
"gcc" to hhl-relocation.  When you run a symlinked program,
hhl-relocation intercepts the call, sets the environment variables, and
then calls the program + .real.

It does preform relocation, but no it cannot reconfigure the standard
directory to run relocated.  You must use rpm to do that.

--Mark

Paolo Scaffardi wrote:
>
> I suppose hhl-relocation can be used to reconfigure the standard directory
> of the compiler toolkit but it seems it cannot be run (it looks for
> hhl-relocation.real).
>
> Any suggestion?
>
> Thanx,
> Paolo.
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-09-05 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-05  9:19 HARDHAT: hhl-relocation... how to use it? Paolo Scaffardi
2000-09-05 17:14 ` Mark Hatle [this message]

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=39B529F9.654F7A88@mvista.com \
    --to=fray@mvista.com \
    --cc=arsenio@tin.it \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).