Changes between Initial Version and Version 1 of Ticket #69594, comment 12


Ignore:
Timestamp:
Apr 4, 2024, 1:02:24 PM (6 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #69594, comment 12

    initial v1  
    44Yes thank's for info. I'm back to the macports version now.
    55
    6 However I do have good news . In my efforts to start upgrade the totem port, I first needed to add some extra ports like libhandy and so on. That resulted finally in the ticket [https://trac.macports.org/ticket/69603 
    7 ] Well actually since I downgraded the clang to version 14 and llvm to 14 . Totem 3.38.2 builds perfect and does run fine. No segfault anymore.
    8 kencu closed the ticket as it is a duplicate of ticket  #68640 But I'm not so shure it is a duplicate since that ticket is about the same error yes but other packages and only showed up since clang version 17 . By modifying you're change in /opt/mports/macports-ports/_resources/port1.0/compilers/clang_compilers.tcl  to block clang to max 16 now to max 14 looks that all problems are solved. Maybe if they find a solution in ticket 68640 to the problem it could be that this also will be good for macos 10.13.6 and below to work with higher clang then what I now could find is 14.
     6However I do have good news . In my efforts to start upgrade the totem port, I first needed to add some extra ports like libhandy and so on. That resulted finally in the ticket #69603 
     7Well actually since I downgraded the clang to version 14 and llvm to 14 . Totem 3.38.2 builds perfect and does run fine. No segfault anymore.
     8kencu closed the ticket as it is a duplicate of ticket  #68640 But I'm not so shure it is a duplicate since that ticket is about the same error yes but other packages and only showed up since clang version 17 . By modifying you're change in /opt/mports/macports-ports/_resources/port1.0/compilers/clang_compilers.tcl  to block clang to max 16 now to max 14 looks that all problems are solved. Maybe if they find a solution in ticket #68640 to the problem it could be that this also will be good for macos 10.13.6 and below to work with higher clang then what I now could find is 14.
    99
    1010