-
-
Notifications
You must be signed in to change notification settings - Fork 12.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing universal boost fails with "Failed changing install name" #7852
Comments
CC @woodruffw for thoughts. This may just result in us dropping |
I'm building boost now to test this locally, but my bet is that they've just removed i386 support for Boost.Chrono. If that's the case, our options are disabling |
Interestingly, $ otool -L /usr/local/Cellar/boost/1.62.0/lib/libboost_chrono-mt.dylib
/usr/local/Cellar/boost/1.62.0/lib/libboost_chrono-mt.dylib:
/usr/local/opt/boost/lib/libboost_chrono-mt.dylib (compatibility version 0.0.0, current version 0.0.0)
@loader_path/libboost_system-mt.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.4.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) And ruby-macho confirms this:
Edit: The inner exception is:
Since ruby-macho modifies files in non-strict mode for Homebrew, this actually means that both slices failed (i386 and x86_64). Since the output from |
This definitely seems like the right option. Having |
I agree. Providing only one arch is preferable to providing 1.5 arches. That being said, this error is very perplexing - all the relocations seem to have been performed correctly. I'm going to spend a bit more time trying to get to the bottom of it. |
@woodruffw ping on this |
@ilovezfs @MikeMcQuaid I think we should go ahead and disable I'll open the PR in a bit. |
Previously, universal builds had removed several modules from i386/ppc targets to get the build to succeed. This is becoming increasingly unsustainable as i386 and PPC age and are no longer supported. See Homebrew#7852.
Opened #8660. |
Previously, universal builds had removed several modules from i386/ppc targets to get the build to succeed. This is becoming increasingly unsustainable as i386 and PPC age and are no longer supported. See #7852.
Bug reports:
When reinstalling boost with universal, I get an error with "Failed changing install name"
Installing boost without the universal binary works "fine", but then I cannot use both x64 and i386 boost, when compiling my own stuff.
I have also tried with various combinations of
--with-icu4c
,--with-mpi
and--universal
, which all fails in different ways.Log-files are present here: https://gist.github.com/anonymous/e1f7a08dc18cc1102608e847a1d2d6c7
The text was updated successfully, but these errors were encountered: