[MacPorts] #38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names ----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: tiff ----------------------------+-------------------------------- After an upgrade today, I had libtiff upgraded from 3.9.7_0 to 4.0.3_1. System is Since that, install_name_tool fails when I make a bundle of an app of mine : install_name_tool: changing install names or rpaths can't be redone for: /Users/otbval/Dashboard/nightly/Monteverdi2-Release/build/_CPack_Packages/Darwin/Bundle/Monteverdi2-0.1.0-Darwin/Monteverdi2-0.1.app/Contents/Resources/MacOS/libtiff.5.dylib (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names) Never seen this message before. I successfully ran install_name_tool on libtiff coming from macport, since a long time. So this is a regression to me. How about putting this -headerpad_max_install_names link flag in the port? -- Ticket URL: <https://trac.macports.org/ticket/38202> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by ryandesign@…): Ok. We've also talked about maybe adding that flag globally, but I can't find the ticket right now. -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by julien.malik@…): See also #36841 (fix applied) and #23372 (won't fix). -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by julien.malik@…): Every cmake-based software is built with that flag by default : http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/Platform/Darwin.cmake;h... -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by julien.malik@…): I have forked the 4.0.3_1 version of tiff port in a local port index, added "configure.ldflags-append -headerpad_max_install_names" into the "platform macosx {}" section, and can confirm it solves my issue. -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by suv-sf@…): Replying to [comment:1 ryandesign@…]:
Ok. We've also talked about maybe adding that flag globally, but I can't find the ticket right now.
See #29838 “Generate shared libraries what can be processed with install_name_tool (one step toward shared library relocation)” -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Comment (by ryandesign@…): Thanks! I've adjusted the title of that ticket to help find it in the future. -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiff | -----------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: MacPorts base now does use `-headerpad_max_install_names` by default. Has that fixed this problem? -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#38202: tiff @4.0.3_1 install_name_tool fails and suggest -headerpad_max_install_names -----------------------------+-------------------------------- Reporter: julien.malik@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: tiff | -----------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Old description:
After an upgrade today, I had libtiff upgraded from 3.9.7_0 to 4.0.3_1. System is
Since that, install_name_tool fails when I make a bundle of an app of mine :
install_name_tool: changing install names or rpaths can't be redone for: /Users/otbval/Dashboard/nightly/Monteverdi2-Release/build/_CPack_Packages/Darwin/Bundle/Monteverdi2-0.1.0-Darwin/Monteverdi2-0.1.app/Contents/Resources/MacOS/libtiff.5.dylib (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names)
Never seen this message before. I successfully ran install_name_tool on libtiff coming from macport, since a long time. So this is a regression to me.
How about putting this -headerpad_max_install_names link flag in the port?
New description: After an upgrade today, I had libtiff upgraded from 3.9.7_0 to 4.0.3_1. System is Since that, install_name_tool fails when I make a bundle of an app of mine : `install_name_tool: changing install names or rpaths can't be redone for: /Users/otbval/Dashboard/nightly/Monteverdi2-Release/build/_CPack_Packages/Darwin/Bundle/Monteverdi2-0.1.0-Darwin/Monteverdi2-0.1.app/Contents/Resources/MacOS/libtiff.5.dylib (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names)` Never seen this message before. I successfully ran `install_name_tool` on libtiff coming from macport, since a long time. So this is a regression to me. How about putting this `-headerpad_max_install_names` link flag in the port? -- Comment: Assuming it has been. -- Ticket URL: <https://trac.macports.org/ticket/38202#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts