(In reply to Paulo Andrade from comment #0)
Hi Paulo,

> From my understanding, this is due to ld merging comment sections,
> and workarounds should be either pass --build-id=none to the linker,
> or --remove-section=.note.gnu.build-id to strip.
> 
>   Can you please clarify if my assumption is incorrect, and the
> build-id is expected to not be removed by strip-unneeded.

It is not expected to be removed by strip-unneeded.  That option is 
intended to remove unneeded *symbols* as well as debug sections.  It
is not intended to remove sections which might be considered to be
of no use, eg because they are not loaded at runtime.  In particular
the option does not remove any ELF format NOTE sections, such as the
.note.gnu.build-id.

(The linker's merging of comment sections is unrelated to this issue).

Also, it is worth mentionining that the .note.gnu.build-id section
*is* needed in an executable binary.  At least in one where the debug
information has been moved into a separate debuginfo file.  In this
sceanario the build-id is also copied to the debuginfo file and it
can be used by tools which consume the debug information, eg gdb, to
verify that the debug info does indeeed apply to the binary to which
it is linked.  (And that the binary has not changed version since
the debug info was created).

The workarounds you mention should be effective, although I do wonder
why you want to use them.  The build-ids are small and do not impeed
the execution of a program, so why remove them ?

Does this explanation help ?

Cheers
  Nick

I am going to close this BZ as I believe that I have answered the questions raised.  If there are any further points that need to be reviewed or considered, please reopen this BZ.

Thanks. The related customer support case had also been closed after your response.