| 1 |
Hmm... I didn't read the original post all the way through before |
| 2 |
responding previously. |
| 3 |
|
| 4 |
It sounds like a pretty niche requirement. I don't see why you |
| 5 |
couldn't just write your own tool to do it for yourself. |
| 6 |
|
| 7 |
Incidentally, this isn't compiling, but *linking*. You could probably |
| 8 |
look at the "prelink" code to get an idea of how to do it. |
| 9 |
|
| 10 |
On Sat, Jun 22, 2013 at 6:05 AM, Anthony G. Basile |
| 11 |
<basile@××××××××××××××.edu> wrote: |
| 12 |
> On 06/21/2013 08:23 PM, Mike Frysinger wrote: |
| 13 |
>> |
| 14 |
>> On Friday 31 May 2013 14:11:01 Christopher Friedt wrote: |
| 15 |
>>> |
| 16 |
>>> strip --strip-unneeded |
| 17 |
>> |
| 18 |
>> |
| 19 |
>> doesn't removed symbols that are exported in a shared lib |
| 20 |
>> -mike |
| 21 |
>> |
| 22 |
> |
| 23 |
> and shouldn't. How can a shared library know what symbols will be consumed |
| 24 |
> in the future by objects linking against it? |
| 25 |
> |
| 26 |
> -- |
| 27 |
> Anthony G. Basile, Ph. D. |
| 28 |
> Chair of Information Technology |
| 29 |
> D'Youville College |
| 30 |
> Buffalo, NY 14201 |
| 31 |
> (716) 829-8197 |
| 32 |
> |
Archives