public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Tomasz Dziendzielski via Libc-help <libc-help@sourceware.org>
Cc: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
Subject: Re: Missing CFLAGS for some objects
Date: Fri, 21 Apr 2023 18:14:17 +0200	[thread overview]
Message-ID: <87r0sdmcva.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAJkqNs1UBtMenz8=9bEMpy0ZoK-GuBy15w=vpSu9dNMiHLSmZw@mail.gmail.com> (Tomasz Dziendzielski via Libc-help's message of "Fri, 21 Apr 2023 13:45:51 +0200")

* Tomasz Dziendzielski via Libc-help:

> Hello,
> one of our developers reported that when we build libc in our environment
> using Yocto Project we end up with corrupted debug symbols even though the
> -g flag is passed to the CFLAGS variable. I noticed that in fact some gcc
> commands (about ~300) are missing -g flag in the invocation. So now my
> question is: is there some reason why some objects are built without CFLAGS?
> You can get the list of objects without debug symbols (and CFLAGS) by
> setting CFLAGS=" -g " for make and using grep for gcc or cross gcc in the
> make execution log file and grep with an invert match for ' -g '.

Those are all linker invocations as far as I can see?  The -g flag will
be dropped by the compiler anyway.

Thanks,
Florian


  reply	other threads:[~2023-04-21 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 11:45 Tomasz Dziendzielski
2023-04-21 16:14 ` Florian Weimer [this message]
     [not found]   ` <CAJkqNs1dTX4rtgfhRrAhRXXCS2LY3tf4poj=ojAv+Chpd6dkxg@mail.gmail.com>
2023-04-27 15:01     ` Adhemerval Zanella Netto

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=87r0sdmcva.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=tomasz.dziendzielski@gmail.com \
    /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).