[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41236] Configure fails to find Qt frameworks

From: Michael C. Grant
Subject: [Octave-bug-tracker] [bug #41236] Configure fails to find Qt frameworks if not installed in system locations (patch provided)
Date: Wed, 15 Jan 2014 16:03:36 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.73.11 (KHTML, like Gecko) Version/7.0.1 Safari/537.73.11

Follow-up Comment #7, bug #41236 (project octave):

Argh, that's not enough. Libtool is a problem too. I actually knew
that---indeed, when I first submitted this patch, I forgot that I was still
using a patched libtool. I've been trying to see if the problem could be
corrected solely from within configure, but it seems it can't.

Everything is fine when the GUI *libraries* are built and linked. The problem
is that libtool doesn't know that "-F/usr/local/Cellar/qt/4.8.5/lib" or its
"-Wl,-F" equivalent is something that needs to be propagated as a dependency.
As a result, the final link doesn't get to see these flags.

Interestingly, the "-Wl,-framework -Wl,Carbon" flags aren't being propagated
either, but that's not proving to be a problem, I presume because Carbon is
not in fact being used.

So basically, libtool *also* has to be patched so that it can propagate -F
flags the same way it propagates -L flags. It already does the right thing
with "-framework" arguments, which is why we haven't seen this before. It's
only for non-system frameworks (rather, frameworks not installed on the system
path) where this becomes an issue.

I do have a patch for libtool, too, and I'm in conversation with them. They're
open to including it, but in the meanwhile, it might be worthwhile to use a
fixed libtool script.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]