From: Viswanath <rviswanathreddy@gmail.com>
To: "David Daney" <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Gprofiling Missing gcrt1.o Object file
Date: Thu, 18 Dec 2008 23:04:32 +0530 [thread overview]
Message-ID: <f2e0c4580812180934v33a9c19fg19ecdaca1e5394bd@mail.gmail.com> (raw)
In-Reply-To: <494A8141.2050006@caviumnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
am planning to cross compile gcrt1.c (source files )with mips-linux-gcc.
Will let you know the output.
Thanks
--viswanath reddy
On Thu, Dec 18, 2008 at 10:28 PM, David Daney <ddaney@caviumnetworks.com>wrote:
> Viswanath wrote:
>
>> Hi,
>> I am trying to profile (gprof profiling) my application which is
>> cross-compiled for the target Mips system [*Linux Mips 2.6.8.1]* and UCLIBC
>> *uclibc-crosstools_gcc-3.4.2_uclibc-20050502. *As far as i searched in the
>> google i could see a requirement of gcrt1.o object file for the mips linux
>> which is not available on the mips-linux.
>>
>> I tried linking with crt1.o but i could not get accurate
>> profiling information. I came to know that gcrt1.o is required to get the
>> accurate information. Where can i get the so called gcrt1.o for Mips-linux.
>>
>>
> gcrt1.o should be part of the C library (uClibc in your case). If it is
> not providing it, it is a bug in uClibc.
>
> Actually I don't even know it uClibc supplies a gcrt1.o. Our build doesn't
> seem to have one. If you build a glibc based system, that would give you a
> working gcrt1.o
>
> David Daney
>
[-- Attachment #2: Type: text/html, Size: 1715 bytes --]
prev parent reply other threads:[~2008-12-18 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 14:06 Gprofiling Missing gcrt1.o Object file Viswanath
2008-12-18 16:58 ` David Daney
2008-12-18 17:34 ` Viswanath [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=f2e0c4580812180934v33a9c19fg19ecdaca1e5394bd@mail.gmail.com \
--to=rviswanathreddy@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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