From: "Sanjay Chadha" <sanjay@s5systems.com>
To: <binutils@sourceware.org>
Subject: Re: [PATCH] enabling gprof for cross builds
Date: Mon, 09 Apr 2007 17:46:00 -0000 [thread overview]
Message-ID: <000301c77ace$ee740120$1f28a8c0@Alps> (raw)
I have a question regarding cross compiling gprof. There was a patch
which removed from gprof from native_only list.
-native_only="autoconf automake libtool fileutils find gawk gettext gzip
hello indent m4 rcs recode sed shellutils tar textutils uudecode wdiff
gprof target-groff guile perl time ash bash bzip2 prms gnuserv
target-gperf"
+native_only="autoconf automake libtool fileutils find gawk gettext gzip
hello indent m4 rcs recode sed shellutils tar textutils uudecode wdiff
target-groff guile perl time ash bash bzip2 prms gnuserv target-gperf"
I am not sure if above change alone will make gprof cross compile (and
link). gprof uses libbfd.a which is compiled as a host_libs hence there
would be a mismatch between gprof and libbfd.a. To circumvent this I
gave the following command (so both host and target are the target mips
platform)
[schadha@devjava1-fc4 binutils-2.15.91.0.2]$ ./configure
--target=mipsel-linux --host==mipsel-linux
[schadha@devjava1-fc4 binutils-2.15.91.0.2]$ make
However the compiled gprof was compiled for the host (i386) machine. Any
ideas of what other changes may be required to cross compile gprof for
the mips machine.
Regards,
Sanjay
S5 Systems - providing custom embedded engineering services
Direct: (613) 226-4764
Mobile: (613) 355-9298
next reply other threads:[~2007-04-09 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 17:46 Sanjay Chadha [this message]
2007-04-12 4:08 ` Ben Elliston
2007-04-12 15:13 ` Danny Backx
2007-04-13 1:09 ` John Tytgat
2007-04-19 21:54 ` Danny Backx
2007-04-20 14:28 ` Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2006-05-08 23:48 Mark Shinwell
2006-05-09 1:38 ` Daniel Jacobowitz
2006-05-09 2:05 ` Ben Elliston
2006-05-09 20:33 ` Mark Shinwell
2006-05-24 12:31 ` Mark Shinwell
2006-05-24 14:28 ` Daniel Jacobowitz
2006-05-24 17:09 ` Mark Shinwell
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='000301c77ace$ee740120$1f28a8c0@Alps' \
--to=sanjay@s5systems.com \
--cc=binutils@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).