On 2019-02-02, at 8:01 AM, Uli Wienands wrote:
> Some progress: > > I followed Ken's suggestion below (clean and try again). Now the logfile > revealed that it was missing libreadline.7.dylib, which caused generation of > the make file to fail. > Sure enough, I have libreadline.8.dylib. Macports does not have the > presumably older version 7 anymore. > Got myself out of that one by manually creating a link to > libreadline.8.0.dylib from libreadline.7.dylib. Crossed fingers & tried > again: Success. gtk-doc is now installed. (All this hassle for updating by > one minor incremental release... sheesh!). That might work for getting past a frustrated moment, but you'll want to remove that symlink ASAP and rebuild whichever port couldn't find libreadline.7.dylib (almost certainly it's "gawk" which is a notable PITA every time we update readline for this issue. > > Next step is that gnutls does not want to build. I get a message about it > cannot build with autoconf-archive being active. yep, we already worked out that one. You just have to disable autoconf-archive, with the instructions in the message. Takes 10 seconds. If somebody has some days to spend on it, it might be possible to change gnutls to not break with autoconf-archive is installed -- that is a project I have no interest in taking on. > I'll have to put this down for now as some real work needs to get done first. > > Ryan suggested I file a bug report, unfortunately none of my browsers on this > 10.6.8 system work with Github so that has to wait until I get back to my > more modern machine. > > I am not giving up yet. No need to give up. Leave mpv on stock SL with me; I thought that worked already. GitHub is changing it's backend frequently lately -- hopefully we can find some way to use it that works with slightly older Firefox versions. (Some GitHub mobile site, perhaps). I use "epiphany" but the last few gnutls updates broke it, so i can't recommend that for general use at present. We'll get there! Ken > > Uli > > On 2/2/19 12:05 AM, Ken Cunningham wrote: >> On 2019-02-01, at 8:21 PM, Uli Wienands wrote: >> >>> Ken, thanks. >>> >>> I did as you suggested (having clang 5 already installed some time ago). >>> >>> It installs a lot of dependencies that it did not try before. It even >>> updated clang 5.0 itself (which I don't really appreciate) Eventually it >>> craps out on gtk-doc, with an error during configuration (somewhat >>> unusual).. Now, why gtk-doc is required is beyond me; I can certainly live >>> without documentations. Also, I have a bunch of gtkdoc-<something> files in >>> /opt/local/bin so I think I may hae gtk-doc already. >>> >>> Anyway, stuck again. Log attached. >> >> I see: >> >> This file was extended by gtk-doc config.status 1.29, which was >> generated by GNU Autoconf 2.69. Invocation command line was >> >> CONFIG_FILES = >> CONFIG_HEADERS = >> CONFIG_LINKS = >> CONFIG_COMMANDS = >> $ ./config.status >> >> on mbp-17 >> >> config.status:1261: creating Makefile >> config.status:1413: error: could not create Makefile >> >> >> Which is a weird error --- is your disk full or something? >> >> anyway, >> >> sudo port clean gtk-doc >> sudo port -v install gtk-doc >> >> should work, did for me: >> >> $ port -v installed gtk-doc >> The following ports are currently installed: >> gtk-doc @1.29_2+python36 (active) platform='darwin 10' archs='noarch' >> date='2019-01-06T17:27:05-0800' >> >> >> >> Ken >> >> >> >> >>> Uli >>> >>> >>> On 2/1/19 12:04 AM, Ken Cunningham wrote: >>>> I am sorry to hear that. Almost every port builds for me on 10.6.8. There >>>> are few exceptions these days -- only MacOS SDK issues. >>>> >>>> But unfortunately the blacklisting and whitelisting and fallbacks in >>>> MacPorts don't always work out, as hard as we try to make it happen. >>>> >>>> I default to build every port with clang-5.0 these days, by setting this >>>> in "/opt/local/etc/macports/macports.conf" >>>> >>>> default_compilers macports-clang-5.0 macports-clang-3.9 >>>> macports-clang-3.8 macports-clang-3.7 gcc-4.2 llvm-gcc-4.2 apple-gcc-4.2 >>>> apple-gcc-4.0 gcc-4.2 gcc-4.0 >>>> >>>> IF you would like to get MPlayer to build, you most likely would have >>>> success doing the same, or for a one-off build, do something like this: >>>> >>>> sudo port clean MPlayer >>>> >>>> sudo port -v install MPlayer configure.compiler=macports-clang-5.0 >>>> >>>> I dream of the day that all of MacPorts is set up to: >>>> >>>> 1. use libc++I for every build >>>> 2. use clang-5.0 or newer for every build >>>> >>>> but in the meantime you may need to force a compiler as I showed above. >>>> >>>> It does work: >>>> >>>> $ port -v installed mplayer >>>> The following ports are currently installed: >>>> MPlayer @1.3.0_3 (active) platform='darwin 10' archs='x86_64' >>>> date='2019-01-22T19:47:43-0800' >>>> >>>> >>>> as far back as 10.4 on all systems. >>>> >>>> >>>> Best, >>>> >>>> Ken >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 2019-01-31, at 9:10 PM, Uli Wienands wrote: >>>> >>>>> Tried to build ir on 10.6 but no luck. Craps out on MPlayer. >>>>> >>>>> log attached. >>>>> >>>>> Any hint would be welcome >>>>> >>>>> Uli >>>>> >>>>> >>>>> >>>>> On 1/31/19 2:25 PM, Ken Cunningham wrote: >>>>>> Some folks over in the MacRumors forums noticed this `smtube` YouTube >>>>>> mini-browser works very nicely on older systems (10.7 and less). >>>>>> >>>>>> I put together a port for it, and I have to say I'm pleased with the >>>>>> performance as well. >>>>>> >>>>>> If you're interested and have an older system like this, please consider >>>>>> giving it a try! >>>>>> >>>>>> Ken >>>>> <main.lg.zip> >>> <config.log.zip> >
