[MacPorts] #46942: gnuplot 5.0.0 +aquaterm fails to include support for aquaterm

[MacPorts]

#46942: gnuplot 5.0.0 +aquaterm fails to include support for aquaterm
--------------------------+---------------------
  Reporter:  michaelld@…  |      Owner:  mojca@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.3.3
Resolution:               |   Keywords:
      Port:  gnuplot      |
--------------------------+---------------------

Comment (by mojca@…):

 Replying to [ticket:46942 michaelld@…]:
 > The configure patch from 4.6.6 was not ported to 5.0.0, so gnuplot now
 fails to find the Aquaterm header, but does not fail building; it just
 does not support the "aqua" terminal even with the +aquaterm set.

 It's not that I didn't port it. But I'm unable to reproduce the failure.

 > At least for me running 10.8, Xcode 5.1.1 (but, I think this will be
 generic since it's a compiler arguments issue rather than OS related).
 > {{{
 > configure:8866: checking for Aquaterm framework presence
 > configure:8887: /usr/bin/clang -o conftest -pipe -Os -arch x86_64
 -I/opt/local/include -I/opt/local/include   -I/opt/local/include
 -L/opt/local/lib -Wl,-headerpad_max_install_names
 -F/opt/local/Library/Frameworks -arch x86_64 -L/opt/local/lib -lcerf
 -framework Foundation -framework Aquaterm conftest.m  >&5
 > conftest.m:32:9: fatal error: 'Aquaterm/AQTAdapter.h' file not found
 > #import <Aquaterm/AQTAdapter.h>
 > }}}
 >
 > I think the "right" solution is to recreate the configure patch;

 I tried to convince the upstream to support `--with-aquaterm=PATH`, but
 they didn't understand my patch and they thought it was too complicated.
 Eventually they started supporting `--with[out]-aquaterm` in some very
 limited way. Maybe someone should ask the autotools developers to
 introduce a macro to search for frameworks on Mac.

 I could reintroduce the previous patch in MacPorts, but I first need to
 understand why this approach doesn't work for you.

 > an alternative that might work is to set some *FLAGS in the
 configure.env.

 I did.
 {{{
 configure.cflags-append     "-F${frameworks_dir}"
 configure.ldflags-append    "-F${frameworks_dir}"
 }}}
 What I don't understand is why your compiler doesn't find the framework
 despite `-F/opt/local/Library/Frameworks`. After all my patch for
 `configure` didn't do anything else but add that flag, except maybe to a
 different location.

-- 
Ticket URL: <https://trac.macports.org/ticket/46942#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X