From: Nureddin Kamadan <nkamadan@sabanciuniv.edu>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcov tool in cross compiling
Date: Wed, 14 Jul 2021 08:42:53 +0300 [thread overview]
Message-ID: <CAP7f7-COM8p7h9ujn797Er78iJomnsG+=JLskFBm5W-Sf3TeAw@mail.gmail.com> (raw)
In-Reply-To: <20210713184216.GS1583@gate.crashing.org>
Hi,
Thank you for the reply, I had compiled with both glibc and newlib. Now, I
am going to try to compile on a QEMU machine.
Best regards,
Nureddin
On Tue, Jul 13, 2021 at 9:44 PM Segher Boessenkool <
segher@kernel.crashing.org> wrote:
> Hi!
>
> On Tue, Jul 13, 2021 at 03:36:10PM +0300, Nureddin Kamadan wrote:
> > I am working on a research project where I need to compile a cross
> compiler
> > (host=x86-linux-ubuntu and target= powerpc-elf).
>
> > My problem is that after compiling the cross
> > compiler, libgcov.a results in having dummy functions and empty object
> > files (I objdumped libgcov.a in every stage of compiling the cross
> > compiler.) I have found out the flag (inhibit_libc) which causes this to
> > happen was being defined while compiling the first stage gcc.
>
> gcov requires a working C library to be able to work. You need to
> compile with support for one. The usual approach is to use a native
> hosted system, but gcov has support for various cross setups as well.
>
>
> Segher
>
next prev parent reply other threads:[~2021-07-14 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 12:36 Nureddin Kamadan
2021-07-13 18:42 ` Segher Boessenkool
2021-07-14 5:42 ` Nureddin Kamadan [this message]
2021-07-14 5:55 ` Sebastian Huber
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='CAP7f7-COM8p7h9ujn797Er78iJomnsG+=JLskFBm5W-Sf3TeAw@mail.gmail.com' \
--to=nkamadan@sabanciuniv.edu \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).