| 1 |
> |
| 2 |
>On 01/08/2017 11:22 AM, tkane1124@××××××××.jp wrote: |
| 3 |
>> Thank you for your reply. |
| 4 |
>> Build.log is attached this mail. |
| 5 |
>> Can you find the error? |
| 6 |
>> |
| 7 |
>> Tkane |
| 8 |
>> |
| 9 |
>> On 01/08/2017 12:01 AM, tkane1124@××××××××.jp |
| 10 |
>> <mailto:tkane1124@××××××××.jp> wrote: |
| 11 |
>> > Hello, |
| 12 |
>> > I want to use dev-lang/R on gentoo/prefix. |
| 13 |
>> > But failed to build libblas as follows. |
| 14 |
>> > How can I fix this failure? |
| 15 |
>> > |
| 16 |
>> > cd |
| 17 |
>> > |
| 18 |
>> /home/kaneko/gentoo/var/tmp/portage/sci-libs/blas-reference-20151113-r1/work/blas-reference-20151113_build/BLAS/SRC |
| 19 |
>> > && /home/kaneko/gentoo/usr/bin/cmake -E cmake_symlink_library |
| 20 |
>> > ../../lib/libblas.so.3.6.0 ../../lib/libblas.so.3 ../../lib/libblas.so |
| 21 |
>> > make[2]: *** [BLAS/SRC/CMakeFiles/blas.dir/build.make:4002: |
| 22 |
>> > lib/libblas.so] Error 1 |
| 23 |
>> > make[2]: *** Deleting file 'lib/libblas.so' |
| 24 |
>> > make[2]: Leaving directory |
| 25 |
>> > |
| 26 |
>> '/home/kaneko/gentoo/var/tmp/portage/sci-libs/blas-reference-20151113-r1/work/blas-reference-20151113_build' |
| 27 |
>> > make[1]: *** [CMakeFiles/Makefile2:1004: |
| 28 |
>> > BLAS/SRC/CMakeFiles/blas.dir/all] Error 2 |
| 29 |
>> > make[1]: Leaving directory |
| 30 |
>> > |
| 31 |
>> '/home/kaneko/gentoo/var/tmp/portage/sci-libs/blas-reference-20151113-r1/work/blas-reference-20151113_build' |
| 32 |
>> > make: *** [Makefile:161: all] Error 2 |
| 33 |
>> > make: Leaving directory |
| 34 |
>> > |
| 35 |
>> '/home/kaneko/gentoo/var/tmp/portage/sci-libs/blas-reference-20151113-r1/work/blas-reference-20151113_build/BLAS' |
| 36 |
>> > * ERROR: sci-libs/blas-reference-20151113-r1::gentoo failed (compile |
| 37 |
>> > phase): |
| 38 |
>> > * emake failed |
| 39 |
>> > |
| 40 |
>> > emerge --info text file is attached. |
| 41 |
>> > |
| 42 |
>> > Tkane |
| 43 |
>> |
| 44 |
>> It doesn't look like the error is contained in the snipped you've |
| 45 |
>> provided, it's probably further up in the build log. |
| 46 |
>> |
| 47 |
>> Dan |
| 48 |
>> |
| 49 |
>> |
| 50 |
>> |
| 51 |
> |
| 52 |
>Have you checked the output of `eselect blas` ? It looks like it's |
| 53 |
>failing in the linking stage, leading me to wonder if an implementation |
| 54 |
>is selected. |
| 55 |
> |
| 56 |
>Dan |
| 57 |
> |
| 58 |
> |
| 59 |
Thank you for confirming various things. |
| 60 |
The result of eselect is below. |
| 61 |
|
| 62 |
$ eselect blas |
| 63 |
Usage: eselect blas <action> <options> |
| 64 |
|
| 65 |
Standard actions: |
| 66 |
help Display help text |
| 67 |
usage Display usage information |
| 68 |
version Display version information |
| 69 |
|
| 70 |
Extra actions: |
| 71 |
add <libdir> <file> <implementation> |
| 72 |
Add a new BLAS implementation |
| 73 |
libdir library directory where BLAS implementation is installed (lib, lib64, etc.) |
| 74 |
file path to file containing symlink map |
| 75 |
implementation name of the BLAS implementation |
| 76 |
list List all installed BLAS implementations |
| 77 |
set <implementation> Activate one of the installed BLAS implementations |
| 78 |
implementation implementation name or number (from 'list' action) |
| 79 |
show Print the currently active BLAS implementation |
| 80 |
$ eselect blas list |
| 81 |
$ eselect blas show |
| 82 |
|
| 83 |
|
| 84 |
Tkane |
| 85 |
|
| 86 |
> |
Archives