Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacPorts: "port upgrade outdated" libjxl build failure

mac57mac57

mac57mac57

macrumors 6502a
Original poster
Aug 2, 2024
685
430
Myrtle Beach, SC
I am tracking down some strange behavior in my MacPorts AbiWord 3.x build (extremely slow typing echoing - unusably slow). I decided to ensure that everything was up to date before going too much further, so I issued the command:

sudo port upgrade outdated

There was a large set of outdated ports and MacPorts took off upgrading them. This was successful until libjxl, which fails to build. The log file is attached.

Does anyone have any insights into what the issue/solution to this build failure might be?

Thanks!
 

Attachments

  • lijxl build failure main.log.txt
    569.7 KB · Views: 50
Tips for searching the Forums: Type in „libjxl, search only „This Forum“
- et voilá.
 
I think it will be useful to keep all these MacPorts issues regarding building ports in a single dedicated thread.

Having numerous topics will likely annoy some people who are not using MacPorts (and such topics will tend to be multiple, since port updates often breaks something), make it more difficult to find anything later if needed and reduce chances of getting help (well, at least I am not monitoring new topics regularly, but I usually check notifications for threads which I participated and can recognize).
 
Sounds good @barracuda156. I have started at least two threads on this topic over time. Are you suggesting to re-use one of these permanently or start a new one, to be used for all MacPorts issues?

Given that MacPorts spans a large number of releases, perhaps we need a higher level entity to hold MacPorts discussions, perhaps a new heading in the same forums macOS area that has one heading for each of the major macOS releases? Thoughts?

Meantime, thanks to @saxfun and @barracuda156, I have moved past the libjxl failure and am back on familiar ground... poppler failures! I will keep at it. Since I am doing a full "self update" MacPorts seems to have declared many of my existing ports to be "broken" and hence is rebuilding them from scratch. This means that I am re-encountering all the same issues as the first time, except that this is the second time through and I have a little more background to work with now.
 
mac57mac57 said:
Sounds good @barracuda156. I have started at least two threads on this topic over time. Are you suggesting to re-use one of these permanently or start a new one, to be used for all MacPorts issues?

Given that MacPorts spans a large number of releases, perhaps we need a higher level entity to hold MacPorts discussions, perhaps a new heading in the same forums macOS area that has one heading for each of the major macOS releases? Thoughts?

Meantime, thanks to @saxfun and @barracuda156, I have moved past the libjxl failure and am back on familiar ground... poppler failures! I will keep at it. Since I am doing a full "self update" MacPorts seems to have declared many of my existing ports to be "broken" and hence is rebuilding them from scratch. This means that I am re-encountering all the same issues as the first time, except that this is the second time through and I have a little more background to work with now.
Click to expand...

I would rather keep the dedicated thread for MacPorts on PowerPC in this subforum, otherwise it becomes a mess, and I have no interest to deal with x86 systems (or read hundreds of comments unrelated to powerpc issues). There is also little sense in a non-powerpc thread, IMO: one gets faster and better help for x86/arm64 on official MacPorts issue tracker.

Any thread with a clear title will do, I guess. To make it usable, I suggest slightly formalized way to report breakages: say, every comment about a new problem has a title in bold font with a port name, OS version and ideally port version. If error is very clear, mention that as well.
Something like:

onetbb 2021.13.0 fails to build on 10.5.8
dino 0.4.4 fails to launch with OpenGL error

And the log attached (if no log exists, the copy terminal output with an error). Technically, nothing else is usually needed.

P. S. I think `poppler` issue was addressed in another thread.
 
barracuda156 said:
P. S. I think `poppler` issue was addressed in another thread.
Click to expand...
Indeed! At least for 10.5.8/10.5.9, the fix amounted to removing poppler from the dependencies list in the geeqie port file, if I recall correctly. I'll hunt up my notes and the posts here on the topic and get past it.

I mentioned it only because I have upgraded to the latest MacPorts and the latest port files. I had hoped that this might have been corrected in this version.
 
mac57mac57 said:
Indeed! At least for 10.5.8/10.5.9, the fix amounted to removing poppler from the dependencies list in the geeqie port file, if I recall correctly. I'll hunt up my notes and the posts here on the topic and get past it.

I mentioned it only because I have upgraded to the latest MacPorts and the latest port files. I had hoped that this might have been corrected in this version.
Click to expand...

I think it needs C++20 now, which requires a modern gcc. So the correct fix is to switch to gcc14. (Which makes sense not just for poppler, but for a lot of stuff.)

However, I had enough of trying to fix compilers in MacPorts. Someone there apparently just likes it broken LOL. You either need to convince MacPorts folks to fix it or instead have a local fix. The problem does not exist with 10.6 ppc, where gcc14 is used anyway, but 10.4–10.5 are in trouble.
 
Thanks @barracuda156; I guess for now I will stick with simply deleting poppler... I saw some instructions a while back (perhaps you posted them) for installing gcc14, and it looked daunting. For now I will pass!
 
mac57mac57 said:
Thanks @barracuda156; I guess for now I will stick with simply deleting poppler... I saw some instructions a while back (perhaps you posted them) for installing gcc14, and it looked daunting. For now I will pass!
Click to expand...

@saxfun got it working, so it should be reproducible. Of course, as long as it is just poppler for an app which does not really require it, no big issue, but eventually this is likely to become a problem.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back