Re: A general philosophical question about MacPorts
Ryan Schmidt wrote: > On Feb 19, 2019, at 07:13, S. L. Garwood wrote: > > > So my philosophical question is “Why MacPorts these days?”. > > Same reason as always: to help you install software on your Mac. If > you prefer installing software in a VM running a different OS, by all > means do so, but it's not the same thing. Another philosophical question you might want to ask yourself is "Why macOS these days?" That's only a bit facetious (a large bit, admittedly). If you mostly use a VM, you might be better off just installing that OS on the hardware and replacing macOS. Just a thought. The only reason I use macos at all is because it's unixy. I spend most of my time in full screen X11 using many programs and languages from macports. Even without X11, macports makes it easy to install and upgrade lots of software that would otherwise be cumbersome to install individually, let alone keep up to date. I wasn't even aware that Apple supported macports. Apple doesn't really support X11 like it used to either and it doesn't work quite as well as it does under Linux but it'll do. >From my point of view, macports makes it possible to keep using macOS. Without it, Linux in a VM or replacing macOS altogether would be hard to resist. cheers, raf
whew
OK Your inbox has 14500 mail. mail->backup size exceeded (after 20%) So I was trying to save all your mail using thunderbird The flash in the corner was “m...@tigger.ws: junk mail” not as in mail ‘from mary’ still trying to backup XX
suggestions
Hello, A little embarrassing, but I need some direction. I realize macports user support does not really exactly support the port I need (ffmpeg), I have a feeling someone reading this will know what's up from the brief details I can provide. Please allow me to describe my situation, and where I think I went wrong. I am running snow leopard 10.6, and while I don't expect support to continue forever (if it wasn't ended some time ago here and nearly everywhere, though last I checked Apple still sold snow leopard server software, probably while supplies lasted), I expected to simply stop updating and allow the tools that always worked to freeze at whatever version, and continue working with them as long as possible. ffmpeg and a few other ports are critical to my scripts, and I broke ffmpeg, and can't rev-upgrade. I went a long time without upgrading, then upgraded some ports and everything seemed to work, blew away previous builds. Then on a subsequent upgrade of I think x265, ffmpeg broke. I read about a solution, which was to blow away x265 and rebuild it. That didn't work, though I believe x265 rebuilt, ffmpeg is still broken... the error should look familiar when I call ffmpeg, I get > dyld: Library not loaded: /opt/local/lib/libvpx.5.dylib > Referenced from: /opt/local/bin/ffmpeg > Reason: image not found > Trace/BPT trap the rebuilds for ffmpeg fail with > Error: Failed to fetch libsdl2: Building libsdl2 @2.0.9 on Mac OS X 10.6 > requires the MacOSX10.7.sdk to be present in /Developer/SDKs/ So my understanding, if correct, is a dependency of the next (or current) rev of ffmpeg requires 10.7 SDK, which is never going to be present on my snow leopard box. I don't need the current build of ffmpeg. Last build that worked... was fine. I don't know why I messed with it, but if I can get a working build, I'll just freeze my system and stop upgrading the ports. I would just restore a backup, but I've never restored a Time Machine back up of my system, and I'm not entirely sure I remembed to include /opt in the backups, and they don't appear to be there. I know there is one method... involving git I believe... that I don't have experience with... to check out... the right version that will build completely on 10.6 without trying to use a dependency I can no longer build. I don't want to waste anyone's time with my problems. I thought there might be someone still running snow leopard and ffmpeg subscribed to the list. If not, I would be grateful for some direction or perhaps a better understanding of just how deep my troubles run. And probably direct contact is ok to keep this bs off the listserv. Sorry for the bother, but I have no where else to turn (other than ffmpeg support, that I'd like to keep my problems far away from). All olutions to my previous build issues were solved here, and I wasted some time before I realized I had to ask for help. Thanks for any help provided comments, otherwise please ignore and carry on with the outstanding work. Respectfully, Chilli
Re: A general philosophical question about MacPorts
On Feb 19, 2019, at 07:13, S. L. Garwood wrote: > So my philosophical question is “Why MacPorts these days?”. Same reason as always: to help you install software on your Mac. If you prefer installing software in a VM running a different OS, by all means do so, but it's not the same thing.
A general philosophical question about MacPorts
First let me say I have used MacPorts since 10.6.8. Recently, given the overall Apple direction for MacOS I stopped and asked myself “Why am I doing this?”. I started using Mint Linux on VirtualBox and ported a couple of the simpler apps I use. Mint has come a long way and runs very well on a VBox instance. Data can move easily from MacOS to Mint and vice-versa. True, I have been a *nix user for decades, but a novice (non-*nix user) wouldn’t be using MacPorts anyway. I appreciate all the work the developers have put into MacPorts but to me the handwriting on the wall was when Apple pulled the MacPorts informal support they provided for years. So my philosophical question is “Why MacPorts these days?”.
Re: Error in trace mode
Ryan Schmidt writes: > On Feb 9, 2019, at 13:02, Piet van Oostrum wrote: > >> Ken Cunningham writes: >> >>> due to a weird idiosyncracy, if set autoconf.cmd you need to specify the >>> depends.build stuff after that line. >>> >>> No idea if this can ever be fixed. You just have to "know" this. >>> >> >> Actually, I found out after much trial and error that the solution is >> to add port:autoconf and port:automake not only to depends_build, but >> also to depends_lib. Which of course is weird, as they are not needed >> after the configure phase. And I needed a build dependency on >> pkgconfig, because that is used in configure to check the versions of >> some dependencies. > > Don't add those to depends_lib. Add them to depends_build, after changing > autoconf.cmd. > > Ken, it's not a weird idiosyncrasy; it's just the way it was designed to > work. I've discussed the reason for that design before. In retrospect, > it was probably wrong to design it that way, and we could yet change the > design. Please look up the prior discussion and resume it if you're > interested. I have done it this way. But if that is the way it is supposed to be used, then it should be documented. -- Piet van Oostrum WWW: http://piet.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
