ifeffit, p5-ifeffit, pgplot: add gcc5 variant

[ryandesign (Ryan Carsten Schmidt)]

Can we add a gcc5 variant to ifeffit and make it the default? gcc5 is the latest stable version of gcc.

[ryandesign (Ryan Carsten Schmidt)]

Comments in the port say the same change would need to be made simultaneously in p5-ifeffit and pgplot.

[dbevans (David B. Evans)]

Cc Me!

[dbevans (David B. Evans)]

Replying to ryandesign@…:

Comments in the port say the same change would need to be made simultaneously in p5-ifeffit and pgplot.

Yes, they all need to be built and linked with the same compiler/libraries. In addition, the Makefile.PL used to build p5-ifeffit (which is compiler specific) is autogenerated during the build of ifeffit.

It would probably be a simplification to unify ifeffit and p5-ifeffit.

[ryandesign (Ryan Carsten Schmidt)]

Replying to devans@…:

Yes, they all need to be built and linked with the same compiler/libraries.

Does it make a difference that all the stable MacPorts gcc ports already use the same libraries (from the libgcc port)?

[dbevans (David B. Evans)]

Replying to ryandesign@…:

Replying to devans@…:

Yes, they all need to be built and linked with the same compiler/libraries.

Does it make a difference that all the stable MacPorts gcc ports already use the same libraries (from the libgcc port)?

That wasn't clear to me. Previously, p5-ifeffit was broken due to this type of mismatch with ifeffit and ifeffit didn't recognize plplot and silently built without it for similar reasons. I did what was necessary to make it work.

Doesn't seem to make much difference now anyway, since, according to its ​download page it's considered to be obsolete and hasn't been updated/maintained since 2008. The preferred replacement is ​Larch. Maybe we should port that.

[ryandesign (Ryan Carsten Schmidt)]

Replying to devans@…:

Replying to ryandesign@…:

Replying to devans@…:

Yes, they all need to be built and linked with the same compiler/libraries.

Does it make a difference that all the stable MacPorts gcc ports already use the same libraries (from the libgcc port)?

That wasn't clear to me.

Yup, that was done two years ago in r109291; see #38814.

[mojca (Mojca Miklavec)]

Cc Me!

[mojca (Mojca Miklavec)]

I committed r148587, but I'm not yet sure how to add a runtime dependency on gcc. I changed that because p5-ifeffit build was broken on the buildbot, but I would be grateful if someone could review it.

[mojca (Mojca Miklavec)]

r145996 added the variants to ifeffit.

[dstrubbe (David Strubbe)]

Mojca, the runtime dependencies are automatic from the compilers portgroup.

[mojca (Mojca Miklavec)]

Can you please check if I got other options right? Maybe some of the options are not needed.

If it looks ok, we can probably close the ticket, right?

I still don't fully grasp how the portgroup works, but are you saying that there is no way to tell the portgroup that no runtime dependencies are needed? I can imagine that there is one group of ports that needs a compiler to work (runtime) and another group of ports that only needs fortran to compile the sources and doesn't need a runtime dependency.

[dstrubbe (David Strubbe)]

compilers.enforce_fortran can only be used on a port which is a dependency. I fixed this in r148774. Runtime dependencies are always needed corresponding to the compiler, as far as I know -- if you compile and link, the resulting executable needs libraries provided by the compiler.