Changes between Version 1 and Version 2 of Ticket #68409, comment 12


Ignore:
Timestamp:
Oct 10, 2023, 7:53:03 AM (7 months ago)
Author:
jrabinow
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #68409, comment 12

    v1 v2  
    2020None of these look like good candidates. If there was a libiconv.dylib under `/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk` or `/usr/{local/,}lib/` that would have been an interesting find. Then again, my system is the one with the failing build so it makes sense there's no other good candidate.
    2121
    22 I can't do the following experiment on my system since it will only use the libiconv under my `/opt/local`, but I'd be curious what `otool -L /opt/local/lib/libgit2.1.7.1.dylib` says after a clean build on your machine. Or if you renamed `/opt/local/lib/libiconv*` to something else, does macports libgit2 still build? [[https://github.com/libgit2/libgit2/issues/6472|This issue you linked to above]] might also be [[https://github.com/jrabinow/macports-ports/blob/5a9e10c90889855bfc5fa906f7d428fdc0536838/devel/libgit2/Portfile#L78|relevant]] in this rebuild scenario.
     22I can't do the following experiment on my system since it will only use the libiconv under my `/opt/local`, but I'd be curious what `otool -L /opt/local/lib/libgit2.1.7.1.dylib` says after a clean build on your machine. Or if you renamed `/opt/local/lib/libiconv*` to something else, does macports libgit2 still build? [[https://github.com/libgit2/libgit2/issues/6472|This issue you linked to above]] might be [[https://github.com/jrabinow/macports-ports/blob/5a9e10c90889855bfc5fa906f7d428fdc0536838/devel/libgit2/Portfile#L78|relevant]] in this rebuild scenario.
     23
    2324Word of caution if you choose to run the rename experiment: anything linked to libiconv will be unable to run, and it's a dependency for a lot of things potentially including the shell, GNU coreutils binaries and terminal multiplexers.
    2425