should also say I found octave in the end unusable on 10.6 due to a qt4 error 
that filled the screen output log with useless messages that everwhelmed the 
output.

so don't be too hopeful.

K

> On Jan 21, 2018, at 1:58 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:
> 
> Hi,
> 
>> On 20 Jan 2018, at 8:55 pm, Uli Wienands <wiena...@gmail.com> wrote:
>> 
>> Ok, I did selfupdate Macports and tried again, and indeed it now gets past 
>> this hurdle.
>> 
>> However, at the end it tells me that all compilers are blacklisted & it will 
>> default to first fall-back option (whatever that is)_. It then wants to 
>> install clang 5.0 and llvm 5.0, at which time I said "no" and let the thing 
>> terminate. I really don't want to install another compiler. I have gcc up to 
>> 7 and I don't think clang works particularly well with Snow Leo. (I also 
>> don't think clang 5 would build on Snow Leo).
>> 
>> Tracking this down a little further, it seems that qscintilla-qt4 is unhappy 
>> with my compilers. Trying to install it separately using macport's gcc-6 
>> bombs as gcc-6 does not seem to understand a flag like -Xarch=64 (or 
>> something like this; the log file got clobbered since).
>> 
>> Looking into the portfile for qscintilla-qt4, but I cannot see where it 
>> blacklists compilers. 
>> 
>> Does anyone know how to comple scintilla-qt4 using gcc? Seems hard to 
>> believe this does not work (the same install worked beautifully on a 
>> Raspberry Pi not long ago).
> 
> You should not do this. The compiler defaults are set by the package managers 
> that know what work and what do know.
> 
> Running an OS as old as snow leopard you are likely to find a lot of ports 
> that cannot use the now very outdated system compiler with the OS and need to 
> use a macports supplied one, and one of the clang compilers is generally used 
> here, given the fact clang is the system compiler in more recent OSes. Gcc is 
> not recommended to compile c++ sources, for a number of reasons.
> 
> Just go with what macports wants here. Anything else is likely to cause you 
> troubles.
> 
> Chris
>> 
>> Thanks for you help so far
>> 
>> Uli
>> 
>>> On Jan 20, 2018, at 12:40 AM, Ken Cunningham 
>>> <ken.cunningham.web...@gmail.com> wrote:
>>> 
>>> 
>>> On 2018-01-19, at 9:59 PM, Ken Cunningham wrote:
>>>>> 
>>>>> error:
>>>>> 
>>>>> :info:build Undefined symbols:
>>>>> :info:build   "_strnlen", referenced from:
>>>>> :info:build       _main in sldtoppm.o
>>>>> :info:build ld: symbol(s) not found
>>>>> 
>>>> 
>>>> 
>>>> Not clear - I just installed it without any issue, without modifying the 
>>>> portfle ...
>>>> 
>>>> $ port -v installed netpbm
>>>> The following ports are currently installed:
>>>> netpbm @10.81.02_0+x11 (active) platform='darwin 10' archs='x86_64' 
>>>> date='2018-01-19T21:51:00-0800'
>>>> 
>>>> 
>>> 
>>> 
>>> Ah - Ryan fixed it between your attempt and mine 
>>> <https://trac.macports.org/ticket/55716>
>>> 
>>> 
>>> 
>>>> Perhaps you should consider opening a ticket so we can work through this 
>>>> properly. <https://trac.macports.org/newticket>
>>> 
>>> Please don't - it's fixed already.
>>> 
>>> sudo port selfupdate
>>> 
>>> and then try your build again
>>> 
>>> K
>> 

Reply via email to