From: Mark Hatle <mark.hatle@windriver.com>
To: prelink@sourceware.org
Subject: Cross prelink
Date: Fri, 05 Nov 2010 18:53:00 -0000 [thread overview]
Message-ID: <4CD452A0.9090502@windriver.com> (raw)
As part of the recently announced Yocto Project <http://yoctoproject.org>, a
cross-prelinker project was announced. The goal of this project is simply to
centralize the cross-prelinker work that has existed for some time, but not
found a home.
I have been working on putting together the various cross prelink patches that
have been created/posted over the past 7 years or so. These patches were
original written by MontaVista Software, Wind River Systems, and Code Sourcery.
(The ChangeLog.cross attempts to capture the history as much as was possible.)
The sources <http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/> are based
on imports from the prelink SVN tree and the patches mentioned above. The
cross_prelink branch is top of tree. (Master is simply the import of the SVN tree.)
The primary difference between the master SVN tree, and the cross-prelink
project tree is the addition of a cross run-time linker (emulator) that can work
in a cross-development environment. This run-time linker will go through many
of the same steps as ld.so/ldd normally would, but is external of the filesystem
and libc being linked. (Also has the side effect of looking like ldd output so
you now have a way to see what ldd would report on the target architecture
without having to boot it.)
Question -- is there any interest in cleaning up this work and it being included
into the master prelink SVN tree?
If so, any suggestions or guidelines for submission?
--Mark
reply other threads:[~2010-11-05 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CD452A0.9090502@windriver.com \
--to=mark.hatle@windriver.com \
--cc=prelink@sourceware.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).