On 4/4/12 2:01 PM, Alexander Hansen wrote:
> On 4/4/12 9:13 AM, Andrew Ackerman wrote:
>> On 4/3/12 7:28 PM, Alexander Hansen wrote:
>>> On 4/2/12 10:53 AM, Andrew Ackerman wrote:
>>>> On 4/2/12 1:11 PM, Alexander Hansen wrote:
>>>>> On 4/2/12 10:03 AM, Alexander Hansen wrote:
>>>>>> On 4/2/12 9:58 AM, Andrew Ackerman wrote:
>>>>>>>
>>>>>>>
>>>>> <snip>
>>>>>>> By the way, I was able to build octave-x11 on this machine, w/o
>>>>>>> monkeying around with .info files.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Andy
>>>>>> I'm not sure yet.  The information that octave-x11 works but octave
>>>>>> does not does at least help restrict the packages that _could_ be
>>>>>> problematic.  Since the only real difference between octave and
>>>>>> octave-x11 is which version of the FLTK library is used, I'm
>>>>>> suspicious of fltk13-aqua.
>>>>>>
>>>>> Perhaps "grep fontconfig /sw/bin/fltk-config" might show something.
>>>>
>>>> Null, in both cases: my machine in which octave-3.1.1-1 built w/o a
>>>> problem, and in my peskier machine.
>>>>
>>>> -Andy
>>> Still scratching my head on this one.  Maybe capture a build log in /tmp
>>> via "fink -l rebuild octave" and email it to me, and I'll compare with
>>> my own log to see if anything jumps out.
>>
>> Attached.
>> Thanks,
>> Andy
>
> Something jumped. :-)
>
> You have:
>
> Octave is now configured for i386-apple-darwin
>
>     Source directory:            .
>     Installation prefix:         /sw
>     C compiler:                  flag-sort -r gcc  -mieee-fp  -Wall -W
> -Wshadow -Wformat -Wpointer-arith -Wmissing-prototypes
> -Wstrict-prototypes -Wwrite-strings -Wcast-align -Wcast-qual -O3
> -D_THREAD_SAFE -pthread
>     C++ compiler:                flag-sort -r g++  -mieee-fp
> -I/sw/include -I/sw/include/freetype2 -I/sw/include
> -I/usr/X11/include    -Wall -W -Wshadow -Wold-style-cast -Wformat
> -Wpointer-arith -Wwrite-strings -Wcast-align -Wcast-qual -O0
> ...
>
> I have:
>
> Octave is now configured for i386-apple-darwin
>
>     Source directory:            .
>     Installation prefix:         /sw
>     C compiler:                  flag-sort -r gcc  -mieee-fp  -Wall -W
> -Wshadow -Wformat -Wpointer-arith -Wmissing-prototypes
> -Wstrict-prototypes -Wwrite-strings -Wcast-align -Wcast-qual -O3
> -D_THREAD_SAFE -pthread
>     C++ compiler:                flag-sort -r g++  -mieee-fp
> -I/sw/include -I/sw/include/freetype2 -I/sw/include -I/sw/include
> -Wall -W -Wshadow -Wold-style-cast -Wformat -Wpointer-arith
> -Wwrite-strings -Wcast-align -Wcast-qual -O0
> ...
>
> We've got a difference of  a final "-I/usr/X11/include" vs.
> "-I/sw/include", and that appears to be what is causing the difference.
> The question, of course, being where that comes from, as there wasn't
> anything obvious in the output to indicate the cause.
>
> I've got a guess to try, though.  What do you get from running
> "pkg-config --cflags fontconfig" ?

Unsurprisingly (I suppose), on the machine I'm having trouble with, the output 
from that command is -I/usr/X11/include, while on the machine w/o trouble, the 
output is -I/sw/include.
So I guess the next question is how do I set it to -I/sw/include?
-Andy




------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to