Hello all and thanks for committing patches. It seems to have built 
successfully, but fails on a simple "merge" operation. As written elsewhere, I 
took care to manually install curl and pkgconfig.

On command
$ mkvmerge -v -o lplde.mkv cd1.avi + cd2.avi

it gave:
mkvmerge(36577) malloc: *** error for object 0x7fff70726500: pointer being 
freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap

Any idea?

Le 12 juin 2014 à 10:09, Arno Hautala a écrit :

> On Thu, Jun 12, 2014 at 9:16 AM, Clemens Lang <c...@macports.org> wrote:
>> Hi,
>> 
>>>> Ideally it would check if the os already provides 1.9 and use that
>>>> one if it does, else depend on whatever ruby is already installed
>>>> by MP.
>>> 
>>> Isn't that the type of non-reproduceable build that MacPorts tries to avoid?
>> 
>> No. Either the OS has 1.9, then it's used (and never MacPorts' copy), or it
>> doesn't, then MacPorts' copy is always used. So the port does build
>> differently on different OS releases, but still doesn't depend on anything
>> installed or configured by the user. We would certainly want to avoid using
>> MacPorts ruby if it's there and system ruby if it isn't.
> 
> Gotcha, I missed that the check would be based on the OS and not just
> the presence of Ruby.
> 
> -- 
> arno  s  hautala    /-|   a...@alum.wpi.edu
> 
> pgp b2c9d448
> _______________________________________________
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to