Finished `release` profile [optimized + debuginfo] target(s)

[CaptainBlood]

rust based ebuild ends up with that message.
My quick uneducated understanding was that there should be two binaries, one for optimized and another for debuginfo.

There is only one binary...

Should I suspect installed binary is full of debug info cruft?
If so could there be a way to get rid of it?

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

[sam_]

Well, first, it would be stripped on merging anyway by default.

But I'm not sure that's what it means anyway. I think the parts in brackets are a sample/summary of the important parts of the release profile (possibly customised by flags).

Giving a specific Rust ebuild example as well as its full build.log would help with verifying that. You can also inspect the working directory before merging.

[CaptainBlood]

build log on dpaste

Could it be debuginfo increases build time? workspace size?

As striping removes cruft, could it be prevention in the first place to generate a better binary, e.g. size wise?

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "