From: Mike Frysinger <vapier@gentoo.org>
To: Jan Kobler <eng1@koblersystems.de>
Cc: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Adjust paths when cross-compiling
Date: Tue, 21 Sep 2010 16:07:20 -0400 [thread overview]
Message-ID: <201009211607.20880.vapier@gentoo.org> (raw)
In-Reply-To: <4C97C03C.5030103@koblersystems.de>
[-- Attachment #1: Type: Text/Plain, Size: 1264 bytes --]
On Monday, September 20, 2010 16:12:44 Jan Kobler wrote:
> Of course I am looking for the tools which are created for this explicit
> purpose and I like to use them.
>
> I had the suspicion that cross-fix-root and lafilefixer are such tools,
> but I only know their help text and their source code. I would like to
> know more about them, before I call them logged in as root. I don't want
> to corrupt my system by calling it at the wrong time, with the wrong
> command arguments or with the wrong environment variables.
what is unclear about cross-fix-root's help text ? rather than keep answering
e-mails about the same thing, i'd rather improve the output of the util and
point people to that.
$ cross-fix-root
Usage: cross-fix-root <sysroot> <cross-bindir> <cross-prefix>
cross-fix-root <cross-prefix>
cross-fix-root # takes settings from env
Environment variables:
CROSS_COMPILE=<cross-prefix>
(SYSROOT|ROOT|STAGEDIR)=<sysroot>
Description:
Fix library perms and mung paths in libtool linker scripts & random -config
scripts to point to our SYSROOT directory. Add symlinks for the -config
with cross-compiler prefixes as autotool packages will search for them first
when cross-compiling.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-09-21 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 11:03 [gentoo-embedded] Adjust paths when cross-compiling Jan Kobler
2010-09-20 17:39 ` Mike Frysinger
2010-09-20 20:12 ` Jan Kobler
2010-09-21 11:04 ` Enrico Weigelt
2010-09-21 20:07 ` Mike Frysinger [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=201009211607.20880.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=eng1@koblersystems.de \
--cc=gentoo-embedded@lists.gentoo.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