| 1 |
On Tuesday 11 October 2011 10:55:32 Fabian Groffen wrote: |
| 2 |
> On 11-10-2011 10:18:16 -0400, Mike Frysinger wrote: |
| 3 |
> > > For the sake of it, can we try to detect GNU binutils here? Our |
| 4 |
> > > profiles restrict strip, so no immediate problem here if not. |
| 5 |
> > |
| 6 |
> > adding detection here will fix most, but i don't think all, of your |
| 7 |
> > troubles |
| 8 |
> > |
| 9 |
> > the code still unconditionally runs `strip -g` which i'm guessing won't |
| 10 |
> > work for you ... |
| 11 |
> > |
| 12 |
> > also, we only run strip on ELF files. so if you aren't an ELF system, |
| 13 |
> > even fixing the -g won't help. |
| 14 |
> |
| 15 |
> Actually, on Solaris (ELF) the way Portage uses strip will damage the |
| 16 |
> files in such a way that they become unusable. And we're using GNU |
| 17 |
> binutils there. So I guess it's ok to assume here. In the profiles |
| 18 |
> stripping is just disabled everywhere it breaks. |
| 19 |
|
| 20 |
so GNU binutils is broken on Solaris ? the flags that portage uses should be |
| 21 |
safe (by design) when stripping ELF files. |
| 22 |
-mike |
Archives