[MacPorts] #64294: isl @0.24: Does not use -arch flags for all compilations

[MacPorts]

#64294: isl @0.24: Does not use -arch flags for all compilations
---------------------------+------------------------------------------
  Reporter:  barracuda156  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:  fixed         |   Keywords:  PowerPC, Leopard, ppc64, gcc
      Port:  isl           |
---------------------------+------------------------------------------

Comment (by barracuda156):

 Replying to [comment:9 kencu]:
 > when a library changes sufficiently that it can no longer properly
 support the software built against it (an ABI change), by convention it
 changes it’s library name version number, like isl has just done. This
 breaks all existing software using that library, forcing all of it to
 rebuild against the new library.
 >
 > So this is all as expected.
 >
 > Some people try making a symlink from the new version to the old. This
 is nutty, as it won’t work reliably.
 >
 > debian and other linux distros often leave behind the old library
 version, so nothing needs urgent rebuilding, but then builds gradually get
 rebuilt against the new version of the library through natural updates.
 Once everything has rebuilt, they remove the old library. That works, but
 you can see takes lots of organization, and has it’s own many issues, so
 MacPorts does not generally do that unless software can’t build against
 the new library version.
 >
 > So you can either rebuild, or hold back updating isl until you are ready
 to rebuild if you like. Or given you are on PPC where rebuilding gcc is a
 week-long project, you can steal out the old isl libs, if the are
 standalone, and leave those behind like debian does for a while, but there
 are potholes there to avoid and you must know what you are doing!!
 >
 > People are proposing exactly this kind of thing for openssl in a PR
 right now in the PR queue, but I suspect it will not be allowed.

 Got it, thank you!

 Gonna rebuild then, what to do. I just got SSD installed into my Quad
 tonight for 10.6, but 10.5.8 remains on HDD volume for a while.
 (I am just back to the Quad, gonna study your discussion with Iains now.)

 P. S. Since you mentioned openssl (asking here, since the ticket is
 closed): I have noticed you used openssl 1.1.1 in your SLPPC ports, while
 current version is 3.2. Was it for some specific reason or just left
 unupdated?

-- 
Ticket URL: <https://trac.macports.org/ticket/64294#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS