[Top][All Lists]

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

[Octave-bug-tracker] [bug #41133] Build system fails to process -F frame

From: Michael C. Grant
Subject: [Octave-bug-tracker] [bug #41133] Build system fails to process -F framework paths for Qt (Homebrew)
Date: Tue, 07 Jan 2014 14:12:49 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36


                 Summary: Build system fails to process -F framework paths for
Qt (Homebrew)
                 Project: GNU Octave
            Submitted by: mcgrant
            Submitted on: Tue 07 Jan 2014 02:12:48 PM GMT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: Michael C. Grant
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.0
        Operating System: Mac OS



When attempting to build Octave with the GUI enabled using Homebrew, the build
fails for two reasons: 
    1) Qt is packaged as a framework, not a set of shared libraries.
    2) the framework is installed in /usr/local/Cellar/qt/4.8.5, not in the
system framework locations.

A simple patch to configure.ac, supplied here, can solve this first problem.
If you examine it, you'll see that it modifies the use of PKG-CONFIG on
darwin*) platforms so that it can grab not just the -L and -l linker
arguments, but the -F and -framework arguments as well, for QT_LDFLAGS and
QT_LIBS. I strove to design this patch so that it leaves non-Mac platforms
unaffected altogether, and still works for cases where Qt is made available
using libraries instead of frameworks.

However, this still fails, because libtool does not process -F properly, which
is necessary to address the second problem. I manually patched the libtool
that is generated by the configure script, and that patch is also included
here. However, because libtool is *generated* by configure, I do not know if
it is possible for this patch to be applied to the source at all.

I do understand that, in theory, Homebrew can just apply these patches during
the compilation process. I wanted to offer them here however in case you might
wish to ensure that this scenario can succeed without Homebrew. 


File Attachments:

Date: Tue 07 Jan 2014 02:12:48 PM GMT  Name: configure.ac.diff  Size: 1012B  
By: mcgrant

Date: Tue 07 Jan 2014 02:12:48 PM GMT  Name: libtool.diff  Size: 2kB   By:



Reply to this item at:


  Message sent via/by Savannah

reply via email to

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