On Wed, Mar 8, 2017 at 8:42 AM, db wrote:
> On 8 Mar 2017, at 01:10, Ryan Schmidt wrote:
> >> On 7 Mar 2017, at 20:00, Ryan Schmidt wrote:
> >>> That can be an acceptable workaround. Sometimes it has side effects. I
> don't know if it does with this
On 8 Mar 2017, at 01:10, Ryan Schmidt wrote:
>> On 7 Mar 2017, at 20:00, Ryan Schmidt wrote:
>>> That can be an acceptable workaround. Sometimes it has side effects. I
>>> don't know if it does with this port.
>
> In the destroot phase, you should not be attempting to
On Mar 7, 2017, at 13:27, db wrote:
> On 7 Mar 2017, at 20:00, Ryan Schmidt wrote:
>> That can be an acceptable workaround. Sometimes it has side effects. I don't
>> know if it does with this port.
>
> Can you give an example?
Suppose the program builds a dynamic library. The absolute path of
On 7 Mar 2017, at 20:00, Ryan Schmidt wrote:
> That can be an acceptable workaround. Sometimes it has side effects. I don't
> know if it does with this port.
Can you give an example?
Something strange I found is that file copy fails silently, no log whatsoever,
pre-
On Mar 7, 2017, at 12:37, db wrote:
> On 7 Mar 2017, at 17:29, Ryan Schmidt wrote:
>> The Makefile does not support DESTDIR. Ideally, fix the Makefile to support
>> DESTDIR and submit that to the developers.
>
> MacPorts Guide links to
>
On Mar 7, 2017, at 10:15, db wrote:
> I'm trying to port a client that comes with only a makefile, but fail to
> destroot it, although it sort of does if I sudo manually. I attach the log.
>
> https://github.com/tldr-pages/tldr-cpp-client/blob/master/Makefile
>
>
The Makefile does not
I'm trying to port a client that comes with only a makefile, but fail to
destroot it, although it sort of does if I sudo manually. I attach the log.
https://github.com/tldr-pages/tldr-cpp-client/blob/master/Makefile
main.log
Description: Binary data