MacPorts Build Failure - Any Suggestions?

[mac57mac57]

Well... there is good news and bad news... 😲

Good news:

I did "sudo port selfupdate", then "sudo port upgrade outdated" to update MacPorts itself and all the port files (I believe that this is the result of those two commands).

Then I built nnn. Perfect success.
Then I upgraded FastFetch, sxiv and gnumeric, all successful.

Bad News:

I tried to build Abiword-x11: it failed, log attached.
I tried to build Smultron: it failed, log attached.

Will your suggestion of "sudo port sync" help any of this? Is there something else I should be doing to get these two to build successfully?

Thanks!

 

[barracuda156]

Well... there is good news and bad news... 😲

Good news:

I did "sudo port selfupdate", then "sudo port upgrade outdated" to update MacPorts itself and all the port files (I believe that this is the result of those two commands).

Then I built nnn. Perfect success.
Then I upgraded FastFetch, sxiv and gnumeric, all successful.

Bad News:

I tried to build Abiword-x11: it failed, log attached.
I tried to build Smultron: it failed, log attached.

Will your suggestion of "sudo port sync" help any of this? Is there something else I should be doing to get these two to build successfully?

Thanks!

Re abiword-x11: what fails in your case is a dependency, libical. I have suggested how to fix it above. Should be easy to try, just copy-paste the command. Once libical installs, hopefully, proceed with abiword-x11.

Re Smultron: part of the log which is attached does now show actual errors, so no idea at the moment. It may be that 10.5 support was removed completely; more likely though that something wall ill-thought, like deployment target being set to 10.6.
I will take a look at that later, but no promises. I hate Objective C, LOL

 

[barracuda156]

I tried to build Smultron: it failed, log attached.

I have found two versions which might work:
https://github.com/jfmoy/Fraise (more recent fork)

GitHub - flomac/Smultron: A now unsupported Open Source Text Editor for MAC OS X developed originally by Peter Borg

A now unsupported Open Source Text Editor for MAC OS X developed originally by Peter Borg - flomac/Smultron

github.com

I need to get to the PowerMac to say if any of these is usable. If something builds for 10.6 ppc, chances are high it can be fixed for 10.5 too.
Will update on this later today.

 

[mac57mac57]

Once more, I am in your debt @barracuda156. I added " compiler.cxx_standard 2011" to the port file for libical and the build sailed right through and completed successfully. The abiword-x11 build is now presently in the process of grinding through the rest of the dependencies. If all goes well, it will complete sometime overnight.

Meantime, I had a run at porting Geeqie. The build failed miserably, but mercifully it failed quickly. This one involves legitimate coding errors. The error log points to undefined identifiers in the source code, so this one will take some working on. It is not a "simple" build process error. I will have a better look at it tomorrow. I've worked through a few errors like this in other builds in the past. With that in mind, I will also have a look at Smultron and see if there is anything I can fix/jury-rig to get it built.

I will post back tomorrow to let you know how the Abiword-x11 build fared over night.

Thanks as always for your insightful help!

p.s.> this post demonstrates some of the enablement presented by Sorbet and AquaFox. I have done all of the work on this set of ports exclusively from my Sorbet-equipped PowerMac G5 DP, including this post and several others, a feat that would have been impossible under stock Leopard and a "regular" browser. The combination of Sorbet and AquaFox really extends the usable life of these wonderful older machines!

 

[barracuda156]

I have done all of the work on this set of ports exclusively from my Sorbet-equipped PowerMac G5 DP, including this post and several others, a feat that would have been impossible under stock Leopard and a "regular" browser

Why though? MacRumors works fine in TenFourFox, TenFourFox works in Leopard.

 

[mac57mac57]

Abiword-x11 built successfully overnight! Thanks Again!

I have never seen AbiWord v3.x running before; quite a treat to have the upgraded version up and operational (I have and use the Mac OS X native AbiWord 2.4.x quite often).

As to TenFourFox vs. AquaFox, the one is just a version of the other, but as I understand it, AquaFox has more current certificates and has some additional optimizations that TenFourFox doesn't have, hence I tend to use it. Good to squeeze every bit of performance I can out of my old PowerMac G5.

Finally, I have corresponded with the author of Smultron in the past - if I cannot get it to build myself, I will email him and ask for his advice. I'll keep this forum posted as this topic develops.

 

[barracuda156]

Abiword-x11 built successfully overnight! Thanks Again!

I have never seen AbiWord v3.x running before; quite a treat to have the upgraded version up and operational (I have and use the Mac OS X native AbiWord 2.4.x quite often).

As to TenFourFox vs. AquaFox, the one is just a version of the other, but as I understand it, AquaFox has more current certificates and has some additional optimizations that TenFourFox doesn't have, hence I tend to use it. Good to squeeze every bit of performance I can out of my old PowerMac G5.

Finally, I have corresponded with the author of Smultron in the past - if I cannot get it to build myself, I will email him and ask for his advice. I'll keep this forum posted as this topic develops.

I tried to compile 3.7.x versions of Smultron (strictly speaking it’s a fork of it), both failed: https://github.com/jfmoy/Fraise/issues/53
There may be a chance of building this on 10.6.8 with 10.5 target, need to try.

If you contact the developer, that would be nice. Ideally we want this compileable on 10.5 and 10.6 both, with gcc (without blocks).

 

[mac57mac57]

Thanks for the ongoing effort @barracuda156. I am sorry that you were not able to bludgeon it into working either. I will reach out to the developer and see if he can give us a hand here. I have played with this for a few hours myself, but I can't make any progress.

I have been ultimately equally unsuccessful with Geeqie. I have resolved one compile issue and got it to advance past libass, where it initially failed, but now it is stuck at poppler and I cannot work my way around that one - it is a configure error of all things. Logs are attached if you are interested in taking a run at it.

Geeqie sounds like a very useful piece, but I have never used it before, so although I am interested, it is just that... a sort of curiosity.

 

[barracuda156]

Thanks for the ongoing effort @barracuda156. I am sorry that you were not able to bludgeon it into working either. I will reach out to the developer and see if he can give us a hand here. I have played with this for a few hours myself, but I can't make any progress.

I have been ultimately equally unsuccessful with Geeqie. I have resolved one compile issue and got it to advance past libass, where it initially failed, but now it is stuck at poppler and I cannot work my way around that one - it is a configure error of all things. Logs are attached if you are interested in taking a run at it.

Geeqie sounds like a very useful piece, but I have never used it before, so although I am interested, it is just that... a sort of curiosity.

It is a weird error:

> Failed to configure poppler: Invalid value for configure.compiler:

Did you tweak something with MacPorts setting for compiler choice?
Anyway, how about this:

sudo port clean poppler
sudo port -v -n install poppler configure.compiler=macports-gcc-7

 

[barracuda156]

I have been ultimately equally unsuccessful with Geeqie.

I certainly have it: http://macos-powerpc.org/packages/geeqie/

Make sure to fix zenity (one of dependencies): https://github.com/macports/macports-ports/pull/24970/files

 

[mac57mac57]

Thanks as always, @barracuda156. You know, I may just have messed with the port file for this one, adding the compiler line fix you suggested to another issue, just to see if it would help... and then forgoting to reverse it when it did not. I will follow your advice and try again. This may be all my fault. My apologies for potentially wasting your time.

 

[barracuda156]

Thanks as always, @barracuda156. You know, I may just have messed with the port file for this one, adding the compiler line fix you suggested to another issue, just to see if it would help... and then forgoting to reverse it when it did not. I will follow your advice and try again. This may be all my fault. My apologies for potentially wasting your time.

sudo port sync will restore original portfile. If poppler still fails, please attach the complete log (preferably actual log, not terminal output).

 

[mac57mac57]

Thanks again...

I tried both sudo port sync and then install, and then, when that failed, the sequence you suggested:

sudo port clean poppler
sudo port -v -n install poppler configure.compiler=macports-gcc-7

As requested, the full log file from the above "port -v -n install" is attached.

Any and all insights MOST appreciated!

BTW, I have communicated with Smultron's author, and he has pointed me at some new stuff; I will go through it and post back to this forum.

 

[mac57mac57]

Follow up on Smultron v3.6b1.

The author has not kept his earlier versions and so was not able to provide much assistance in that regard (something about Apple forbidding it).

He did point me to an Xcode project for Smultron 3.6b1, but with no experience using Xcode, I had little luck with it. I tried changing all the default build targets, which were 10.6 related, to 10.5, but the build fails with include file errors - missing .h files I expect. Not knowing the source structure, I am at a loss to correct these.

The author did also say that he has no control/influence over the MacPorts versions of Smultron, and so was not able to help there either.

He DID however send me a 3.6 Smultron.app, but it is built for Intel and of course would not run on my PowerMac G5. However, if anyone is interested in getting a Smultron 3.6 (Intel), just reply to this thread and I will post it to a website I own and provide a URL to download it.

Smultron 3.6b1 on MacPorts - a lost cause?

 

[barracuda156]

Thanks again...

I tried both sudo port sync and then install, and then, when that failed, the sequence you suggested:

sudo port clean poppler
sudo port -v -n install poppler configure.compiler=macports-gcc-7

As requested, the full log file from the above "port -v -n install" is attached.

Any and all insights MOST appreciated!

BTW, I have communicated with Smultron's author, and he has pointed me at some new stuff; I will go through it and post back to this forum.

Re poppler: log was useful.

:info:configure   Target "cmTC_a3da4" requires the language dialect "CXX20" .  But the
:info:configure   current compiler "GNU" does not support this, or CMake does not know the
:info:configure   flags to enable it.

A newer gcc is needed.

As a quick and easy solution you could install an earlier version, there is no real need to have the latest poppler. Otherwise you need to build gcc10-bootstrap and use that to build gcc14. Which is the right thing to do in principle, but takes some time and effort.

 

[barracuda156]

Follow up on Smultron v3.6b1.

The author has not kept his earlier versions and so was not able to provide much assistance in that regard (something about Apple forbidding it).

He did point me to an Xcode project for Smultron 3.6b1, but with no experience using Xcode, I had little luck with it. I tried changing all the default build targets, which were 10.6 related, to 10.5, but the build fails with include file errors - missing .h files I expect. Not knowing the source structure, I am at a loss to correct these.

The author did also say that he has no control/influence over the MacPorts versions of Smultron, and so was not able to help there either.

He DID however send me a 3.6 Smultron.app, but it is built for Intel and of course would not run on my PowerMac G5. However, if anyone is interested in getting a Smultron 3.6 (Intel), just reply to this thread and I will post it to a website I own and provide a URL to download it.

Smultron 3.6b1 on MacPorts - a lost cause?

Well, MacPorts version (which is built from unmodified sources) seems to work fine on 10.6 ppc, at least it certainly builds with no hacking around.

If the original developer could look into the source code, it is available from MacPorts.

sudo port extract smultron

He has no control of what MacPorts has (and neither do I), but we can easily add needed patches, if he suggests how to build it for 10.5.

 

[mac57mac57]

Thanks @barracuda156. I have already downloaded the author's 3.6b1 source code, and will play with it outside of Mac Ports to see if I can bludgeon it into building. I'll reach out to the author again if I get completely stuck.

If I can get it built, we can then discuss how to fold it into MacPorts

 

[barracuda156]

Thanks @barracuda156. I have already downloaded the author's 3.6b1 source code, and will play with it outside of Mac Ports to see if I can bludgeon it into building. I'll reach out to the author again if I get completely stuck.

If I can get it built, we can then discuss how to fold it into MacPorts

MacPorts does not do anything special in this case, it simply invokes Xcode anyway.

 

[mac57mac57]

I have continued to work on geeqie. I bypassed the poppler issue for now and the build advanced a long way, then got stuck at gstreamer1, where it is looking for a family of functions with names like "NSApplicationActivationPolicyProhibited". I cannot find where these are defined, and after several hours of working on it, I have to admit defeat - I have no places left to look.

Does anyone recognize this set of NSApplication.... functions and where they are defined? Clearly a .h file is not being included where it should OR there is a dependency that has not been captured correctly.

 

[ChrisCharman]

I have continued to work on geeqie. I bypassed the poppler issue for now and the build advanced a long way, then got stuck at gstreamer1, where it is looking for a family of functions with names like "NSApplicationActivationPolicyProhibited". I cannot find where these are defined, and after several hours of working on it, I have to admit defeat - I have no places left to look.

Does anyone recognize this set of NSApplication.... functions and where they are defined? Clearly a .h file is not being included where it should OR there is a dependency that has not been captured correctly.

Most likely Cocoa or Carbon.

 

[mac57mac57]

Indeed. I hunted them down, and they are included in a series of statements in Cocoa.h, but the line that includes them must refer to the wrong location... since the log files for the Geeqie build say that these are undefined identifiers.

 

[barracuda156]

I have continued to work on geeqie. I bypassed the poppler issue for now and the build advanced a long way, then got stuck at gstreamer1, where it is looking for a family of functions with names like "NSApplicationActivationPolicyProhibited". I cannot find where these are defined, and after several hours of working on it, I have to admit defeat - I have no places left to look.

Does anyone recognize this set of NSApplication.... functions and where they are defined? Clearly a .h file is not being included where it should OR there is a dependency that has not been captured correctly.

AppKit: https://developer.apple.com/documen...olicy/nsapplicationactivationpolicyprohibited
They are present in 10.6+ (perhaps 10a190 already has them, since I do not think I have a custom patch for gstreamer).

There are a few things one can do in such a case:
1. Check if there is an equivalent in earlier SDK (some functions were simply renamed, and then can be conditionally defined to whatever needed, MacPorts has examples of that).
2. If no, check GitHub commit history to see for a version which does not use them yet (gstreamer most probably has such, it is a software with long history).
3. If that is not there as well, try stub them out or put inside ifdef. (To quickly check if the thing compiles without those you could simply delete them.)
Or if there is time and motivation, reimplement some alternative (assuming they are actually needed).

Why gstreamer is even necessary for geany? It could be that MacPorts enables extra stuff in a port which is not strictly required. Delete a dependency from a portfile (and related configure args, if any are specified) and see if configure passes.

 

[mac57mac57]

Delete a dependency from a portfile (and related configure args, if any are specified) and see if configure passes.

funny... that is how I bypassed the poppler issue! Now I guess I can try gstreamer as well.

I can see that Geeqie might need both however. Poppler is a PDF viewer and gstreamer is likely involved in the playback of video. Both of these are reasonable things for an "image viewer" to consider doing. For example, XnView MP incorporates video playback seamlessly - videos are just another "image" to it. The same MIGHT be true of PDF.. haven't tried it.

Anyway, my guess is that if I remove enough dependencies, the build will eventually get to the end, but I don't expect it to link correctly - key parts are missing. However, one step at a time! I'll keep winnowing down the list of dependencies as I can, and keep going. I'll report back.

 

[barracuda156]

funny... that is how I bypassed the poppler issue! Now I guess I can try gstreamer as well.

I can see that Geeqie might need both however. Poppler is a PDF viewer and gstreamer is likely involved in the playback of video. Both of these are reasonable things for an "image viewer" to consider doing. For example, XnView MP incorporates video playback seamlessly - videos are just another "image" to it. The same MIGHT be true of PDF.. haven't tried it.

Anyway, my guess is that if I remove enough dependencies, the build will eventually get to the end, but I don't expect it to link correctly - key parts are missing. However, one step at a time! I'll keep winnowing down the list of dependencies as I can, and keep going. I'll report back.

Anything which can be disabled via configure arguments can be legitimately removed. How desirable is related functionality is another question, but nothing should fail (you may need to specify configure arguments when going against default choice).
Removing something which cannot be removed via configure args will require hacks and may or may not eventually work.

With poppler I really suggest installing an earlier version rather than dropping it completely. That should be perfectly fine.

On a general note, it may be worth checking if MacPorts already has patches that you need. Cocoa stuff is conveniently named with ridiculous and very specific names, those are easy to search. BBEdit / TextWrangler have multi-file search, just run that over macports ports directory (clone github repo, for example).

 

[barracuda156]

Indeed. I hunted them down, and they are included in a series of statements in Cocoa.h, but the line that includes them must refer to the wrong location... since the log files for the Geeqie build say that these are undefined identifiers.

Ok, you won’t find a ready patch, since I tested the build only on 10.6, where it worked fine
But look where these functions were added: https://github.com/GStreamer/gstreamer/commit/1815061e26db11c5e8cef35e7b5e3e3fb9eb7017

Just delete that chunk If it could have been added this way, it can also be thrown away (anyway 10.5 SDK do not have these, it is pointless there).

Let me know if that is sufficient. I can submit a patch to MacPorts, but would rather do everything at once to support 10.5.

P. S. A neat way would be to put them into

#if MAC_OS_X_VERSION_MIN_REQUIRED >= 1060
if ([NSApp activationPolicy] == NSApplicationActivationPolicyProhibited) {
    [NSApp setActivationPolicy:NSApplicationActivationPolicyAccessory];
}
#endif

Add `#include <AvailabilityMacros.h>` in the beginning of the file if it is not already there.