| 1 |
On 13-12-2015 13:24:37 +0100, Askar Bektassov (Аскар Бектасов) wrote: |
| 2 |
> If bootstrap-prefix.sh fails with "$EPREFIX/tmp/etc/portage/make.profile is |
| 3 |
> not a symlink and will probably prevent most merges.", you can replicate |
| 4 |
> macos 10.10 profile (cp -r |
| 5 |
> $EPREFIX/usr/portage/profiles/prefix/darwin/macos/10.10 |
| 6 |
> $EPREFIX/usr/portage/profiles/prefix/darwin/macos/10.11), until such time |
| 7 |
> macos 10.11 is fully supported. |
| 8 |
|
| 9 |
latest tree should have this profile already |
| 10 |
|
| 11 |
> If llvm-3.4.2 compilation fails with "ld: library not found for -lc++", make |
| 12 |
> sure that xcode command line tools are used instead of full Xcode 7 package |
| 13 |
> (sudo xcode-select -s /Library/Developer/CommandLineTools). |
| 14 |
|
| 15 |
I think I've fixed that, not sure |
| 16 |
|
| 17 |
> If perl-5.22.0 compilation fails with "ld: library not found for |
| 18 |
> -lgcc_s.10.4", you can create the missing symlink (ln |
| 19 |
> -s /usr/lib/libgcc_s.1.dylib $EPREFIX/usr/lib/libgcc_s.10.4.dylib). This is |
| 20 |
> a known bug [1]. |
| 21 |
|
| 22 |
I believe I've fixed this. Perl insists on a deployment target of 10.3 |
| 23 |
(Panther, that's before Tiger, Leopard, Snow Leopard, Lion, Mountain |
| 24 |
Lion, Mavericks, Yosemite and El Capitan) and I forced to override that |
| 25 |
to something recent (== the current platform). |
| 26 |
|
| 27 |
> If python-3.3.3 compilation fails with "dyld: Library not loaded: |
| 28 |
> $EPREFIX/usr/lib/libpython3.3.dylib", you can create the missing symlink (ln |
| 29 |
> -s |
| 30 |
> $EPREFIX/tmp/var/tmp/portage/dev-lang/python-3.3.3/work/x86_64-apple-darwin14/libpython3.3.dylib |
| 31 |
> $EPREFIX/usr/lib/libpython3.3.dylib). |
| 32 |
|
| 33 |
This was a missing DYLD_LIBRARY_PATH issue during install. Python 3.3 |
| 34 |
shouldn't be used/emerged any more though, 2.7.11, 3.4.3 and 3.5.1 are fixed. |
| 35 |
|
| 36 |
> If python-3.3.3 compilation fails with "fatal error: too many errors |
| 37 |
> emitted, stopping now [-ferror-limit=]", you need to download Xcode_6.4.dmg |
| 38 |
> [2], copy MacOSX10.10.sdk from its contents to a location of your preference |
| 39 |
> (cp -rv |
| 40 |
> /Volumes/Xcode/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk |
| 41 |
> $HOME/Downloads) and add SDKROOT variable pointing to that location into |
| 42 |
> your make.conf (echo SDKROOT=$HOME/Downloads/MacOSX10.10.sdk >> |
| 43 |
> $EPREFIX/etc/portage/make.conf). |
| 44 |
|
| 45 |
Ok, interesting. Any idea why? |
| 46 |
|
| 47 |
> If python-3.3.3 installation fails with "Detected file collision(s): |
| 48 |
> $EPREFIX/usr/lib/libpython3.3.dylib", then remove the symlink created above |
| 49 |
> and complete the package merge manually (rm -rf |
| 50 |
> $EPREFIX/usr/lib/libpython3.3.dylib; ebuild |
| 51 |
> $EPREFIX/usr/portage/dev-lang/python/python-3.3.3.ebuild qmerge clean) |
| 52 |
|
| 53 |
I guess this is due to the workaround you did earlier. |
| 54 |
|
| 55 |
> If mhash-1.4 fails with "mhash.c:23:10: fatal error: 'mhash.h' file not |
| 56 |
> found", then comment out the SDKROOT variable in |
| 57 |
> $EPREFIX/etc/portage/make.conf. |
| 58 |
|
| 59 |
ditto |
| 60 |
|
| 61 |
> After any of the above fixes, you can relaunch bootstrap-prefix.sh from the |
| 62 |
> last checkpoint (bootstrap-prefix.sh $EPREFIX stage3). |
| 63 |
> |
| 64 |
> == after completion == |
| 65 |
> |
| 66 |
> If during the script you notice some complaints that some confdir-14B--- |
| 67 |
> folders cannot be deleted, you may need to manually go into the |
| 68 |
> $EPREFIX/tmp/var/tmp folder and delete perform some manual cleaning [3]. |
| 69 |
|
| 70 |
Nice, sounds like a lot should work better now! |
| 71 |
|
| 72 |
Thanks, |
| 73 |
Fabian |
Archives