[m-rev.] for review: Strip executable as a separate step on Mac OS X.

[Julien Fischer]

On Wed, Apr 30, 2014 at 3:54 PM, Julien Fischer <jfischer at opturion.com>wrote:

>
> Hi Peter,
>
>
> On Thu, 20 Mar 2014, Peter Wang wrote:
>
>  On Thu, 20 Mar 2014 13:07:42 +1100 (EST), Julien Fischer <
>> jfischer at opturion.com> wrote:
>>
>>>
>>> I suggest --strip-executable-command (for consistency with
>>> --link-executable-command), rather than --strip-command.
>>>
>>> Also, the option should be publicly documented.
>>>
>>
>> Done.
>>
>
> Actually, doing this breaks dynamically linked executables on Mac OS X
> in some cases.  Specifically, if a program contains a runtime trace goal
> condition and you strip the executable, then dyld cannot find the symbol
> corresponding to the global variable emitted in the _init.c file for
> that runtime condition.
>
> I'm going to disable this until I find a way of stripping executables
> that doesn't break them.  (If you *really* want to strip exectuables
> on Mac OS X you'll have to do so manually for now.)
>

It seems that if --mercury-linkage=shared we need to pass -x to strip,
otherwise if --mercury-linkage=static we can just pass no flags as before.

Cheers.
Julien.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20140430/0bde06bb/attachment.html>