Re: building with AquaTerm

[Hans-Bernhard B. <HBB...@t-...>]

On 10.03.2011 00:41, Mojca Miklavec wrote:
> 2011/3/10 Hans-Bernhard Bröker wrote:
>> On 09.03.2011 22:48, Mojca Miklavec wrote:
>>> 2011/3/9 Hans-Bernhard Bröker wrote:

>>> Here is where all the fun begins. I *have to* install AquaTerm to
>>> /usr/local/...,

>> Says who?  Why?

> If I want to choose the option "a)" (make sure libraries are only in
> places where the compiler already looks by default).

But it seems we've already established that /usr/local is not in your 
compiler's default search paths, either, haven't we?

> I forgot to say: I want my gnuplot to live *outside* of MacPorts.

Then you can _not_ use anything from MacPorts.  None of the libraries, 
none of the headers, possibly not even the compiler.

> However I find it perfectly fine if that personal copy of gnuplot uses
> libraries like pdflib, cairo etc. from MacPorts.

Now you're contradicting yourself.

Just because a program sits in your $HOME/bin doesn't mean it's outside 
of MacPorts.  MacPorts isn't just a directory --- it's a system of 
libraries, environment settings and configuration items that all work 
together.  Any executable built using the libraries from the MacPorts 
system is, for better or for worse, a MacPorts binary.  Even if it sits 
outside MacPorts' directories.

> So how can I for example:
> - Tell gnuplot's configure script to use the version of aquaterm from
> /usr and not the one from /opt (when I have macports in path)?

By making sure /opt appears before /usr on all your header and library 
searches (this is where an explicit -I/-L flag passed to ./configure 
might behave different from a change to environment variables: 
explicitly given directories are searched before default places), and by 
making sure you don't pull in the MacPorts version through some indirect 
connection, e.g. another library taken from MacPorts, which includes 
references to their aquaterm library.

> I know that configure can't read my mind, but:
> - when I have aquaterm under both /usr and /opt, it uses the version from /opt

That could mean your include and library search paths are the wrong way 
round.

> - when I have aquaterm only under /opt, it doesn't compile aquaterm
> support at all (even though it could easily use the version from /opt)

Then you have to dig deeper to find out why it doesn't accept that version.