| 1 |
On Thu, 2018-08-30 at 20:12 +0100, Sergei Trofimovich wrote:
|
| 2 |
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. |
| 3 |
> |
| 4 |
> |
| 5 |
> On Thu, 30 Aug 2018 07:37:16 +0000 |
| 6 |
> Joakim Tjernlund <Joakim.Tjernlund@××××××××.com> wrote: |
| 7 |
> |
| 8 |
> > > > Tweaking ebuild to expand STRIP_MASK for ld.so might help. |
| 9 |
> > > |
| 10 |
> > > OK, can I use STRIP_MASK outside ebuilds, like in /etc/portage/make.conf or |
| 11 |
> > > in my profile? Something like STRIP_MASK="/lib64/ld-* /lib/ld-*" |
| 12 |
> |
| 13 |
> I believe you can't. You would have to resort to /etc/portage/bashrc |
| 14 |
> hacks to override ebuilds' value. Requesting new feature from dev-portage@ |
| 15 |
> sounds reasonable. |
| 16 |
> |
| 17 |
> For example, add STRIP_MASK_USER to be controlled by user. |
| 18 |
> |
| 19 |
> STRIP_MASK is normally used for cases when software breaks when |
| 20 |
> stripped (examples: not-quite-ELF files, not-yet-linked .o files). Not |
| 21 |
> something for convenience or niche purposes. |
| 22 |
> |
| 23 |
> STRIP_MASK_USER might be a good way to fine-grain desired policy |
| 24 |
> of stripping package on top of existing FEATURES=nostrip knob. |
| 25 |
|
| 26 |
Yes, I like this idea with STRIP_MASK_USER
|
| 27 |
|
| 28 |
Jocke |
Archives