Changes between Initial Version and Version 1 of Ticket #63115, comment 15
- Timestamp:
- Jun 24, 2021, 3:21:06 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #63115, comment 15
initial v1 1 Well, most likely we have to rewrite all the libgcc11 libraries with full paths on installation, and probably tweak all the binaries too, if we can't find some more elegant way to configure@rpath off.1 Well, most likely it will be required to rewrite all the libgcc11 libraries with full paths on installation, and probably tweak all the binaries too, if a more elegant procedure to configure gcc to turn @rpath off. 2 2 3 Even if we did tweak gcc11 to supply an additional @rpath reference to where we keep all our libgcc libs by default to all binaries it makes (do-able), all the other gcc versions we usewould not understand that. At the moment the Intel gcc versions aren't using @rpath, but the plan is to add it soon.3 Even if gcc11 were tweaked to supply an additional @rpath reference to where the libgcc libs are by default located to all binaries it makes (do-able), all the other gcc versions used on MacPorts would not understand that. At the moment the Intel gcc versions aren't using @rpath, but the plan is to add it soon. 4 4 5 5 Right now, gcc10 says it is building on arm64, but not sure if it is really building usable software against real libraries, because it will use the libgcc11 libraries which have @rpath in them too. 6 6 7 For the moment, I thinkgcc on arm64 must be just completely broken.7 For the moment, it seems gcc on arm64 must be just completely broken.