orpie: won't link on build - patch included

[jcdenton513@…]

This isn't the most elegant fix I'm sure, but it works and I've successfully linked and ran the application.

As far as I can see, it's looking for libmlgsl.a which is provided by the package ocamlgsl. The orpie source file has that library but it doesn't seem to link correctly. My solution while creating more dependencies, works very well. It'd require ocamlgsl and because it modifies configure.in, it'll need autoconf to build a new configure file.

Once the patch is applied, the program will compile and link and will be ready to install.

[jcdenton513@…]

Cc Me!

[ryandesign@…]

Assigning to maintainer for comment.

[brett@…]

tested here too, looks good

[snb@…]

The patch I just attached, Makefile.in.diff, will force use of ocamlc instead of ocamlc.opt. I'm not sure why, but this also seems to fix the problem for me and doesn't require adding more dependencies or autoconf. Less dependencies seems nice, but I think my fix also isn't necessarily the most elegant :) Either my patch or the reporter's is fine by me to commit.

I should mention that I haven't been using MacPorts lately, so if someone else wants to be maintainer of this port, be my guest.

[jcdenton513@…]

doesn't require autoconf

[jcdenton513@…]

You're solution worked for me.

Concerning my solution, you could drop the modifying the configure file and just insert the variables directly to Makefile.in. The main reason I went the route I did was so if you ran ./configure it'd notice if libmlgsl.a was or wasn't avaliable. Being managed by a MacPorts, it would already know if the dependency was avaliable so checking with configure would be redundant and that step can be left out.

I attached another patch that'll do just that, getting rid of the autoconf requirement.

Whether you use my patch or the other I guess depends on if you want it to use an external library or the static library in orpie's source. The only advantage I can see with my way is if ocamlgsl is updated, orpie will benifit. Unless that upgrade breaks orpie. Both look like they're not actively maintained so it probably wouldn't matter either way. Can't be positive about ocamlgsl though.

[macsforever2000@…]

Cc Me!

[christopher.andrey@…]

Cc Me!

[jmr@…]

So which of these patches should be committed? And are there any portfile changes needed beyond adding patchfiles? Brett, you seem to have figured this out in comment:3.

[snb@…]

As far as I can tell, jcdenton513's patches would require adding a dependency on ocamlgsl to the Portfile. My patch should not necessitate that as it should make orpie use its own version of ocamlgsl. Otherwise just adding patchfiles should be sufficient. It does not matter to me what patch is used, though, and I don't know if any of them actually still work (I don't have a macports installation around to test at the moment).