From: Jan Kobler <eng1@koblersystems.de>
To: gentoo-embedded@lists.gentoo.org
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: Re: [gentoo-embedded] Adjust paths when cross-compiling
Date: Mon, 20 Sep 2010 22:12:44 +0200 [thread overview]
Message-ID: <4C97C03C.5030103@koblersystems.de> (raw)
In-Reply-To: <201009201339.55132.vapier@gentoo.org>
Mike,
sorry for my unclear email.
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.
1. Are there any docs or discussions on the web which further describe
their purpose and their usage?
2. How should I have used these tools in order to prevent the problems with
$ROOT/usr/lib/libgmp.la and
$ROOT/usr/lib/libcrack.so
which I have described in my previous email?
3. Which tools should be called when?
After each emerge?
Are these tools already called by emerge or other system tools?
4. When I cross compile the root file system in
/usr/armv4tl-softfloat-linux-gnueabi,
libdir needs to be
libdir='/usr/armv4tl-softfloat-linux-gnueabi/usr/lib'.
When the target system (ARM) mounts this root fs through NFS, then
libdir needs to be again libdir='/usr/lib'.
May I call cross-fix-root or lafilefixer on the target or host system
again, in order to change the paths forth and back?
Best regards
Jan
next prev parent reply other threads:[~2010-09-20 21:08 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 [this message]
2010-09-21 11:04 ` Enrico Weigelt
2010-09-21 20:07 ` Mike Frysinger
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=4C97C03C.5030103@koblersystems.de \
--to=eng1@koblersystems.de \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=vapier@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