Open salma1601 opened 4 years ago
Dear @salma1601 thank you so much for giving our pipeline package a try!
Of course we recommend using Gentoo, but it's not a prerequisite. It's just what we decided to use on all our servers at the ETH and UZH in Zurich, because it works so well for scientific software. Other labs have reported using the pipelines in Ubuntu.
Regarding your current issue, it is standard policy for Gentoo to prompt you if an installation requires configuration changes to your system. You simply need to accept them.
emerge -v samri --autounmask-continue
would do this automatically.
I notice there is also a license issue. This is a feature of Gentoo allowing you to select what licenses are acceptable for your work. Assuming you are doing academic work, under fair use policy (and barring constraints of your institute), you can do:
echo 'ACCEPT_LICENSE="*"' >> /etc/portage/make.conf
However, since we use a lot of cutting-edge software versions, in order to best get comparability with our work, it might be best to get the very newest versions of packages by also enabling the Chymeric Overlay (these new versions will also be included in Gentoo Science, but that usually takes a few weeks), and enabling all “unstable” versions.
After installing the overlay, do:
echo 'ACCEPT_KEYWORDS="~amd64"' >> /etc/portage/make.conf
After doing this, it might be advisable to first run:
emerge --sync
emerge -vaDNu world #(this updates your system to use unstable versions)
and only thereafter run:
emerge -v samri --autounmask-continue
Let me know if there are further issues. We're happy to include such helpful tips in the README.
Dear @TheChymera
Thank you very much for your help and reactivity. I tried the first command emerge -v samri --autounmask-continue
, and it looks like there is an error with UTF8
and dev-util/meson-0.52.0
. Can I follow the rest of the commands ?
Emerging (46 of 217) dev-util/meson-0.52.0::gentoo
- meson-0.52.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] Unpacking source... Unpacking meson-0.52.0.tar.gz to /home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work Source unpacked in /home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work Preparing source in /home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0 ... Source prepared. Configuring source in /home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0 ...
- Could not find a UTF-8 locale. This may trigger build failures in
- some python packages. Please ensure that a UTF-8 locale is listed in
- /etc/locale.gen and run locale-gen. Source configured. Compiling source in /home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0 ...
- python3_6: running distutils-r1_run_phase distutils-r1_python_compile python3.6 setup.py build -j 3 Traceback (most recent call last): File "setup.py", line 24, in
from setuptools import setup File "/home/salma/gentoo/usr/lib64/python3.6/site-packages/setuptools/init.py", line 18, in import setuptools.version File "/home/salma/gentoo/usr/lib64/python3.6/site-packages/setuptools/version.py", line 1, in import pkg_resources File "/home/salma/gentoo/usr/lib64/python3.6/site-packages/pkg_resources/init.py", line 35, in import plistlib File "/home/salma/gentoo/usr/lib64/python3.6/plistlib.py", line 65, in from xml.parsers.expat import ParserCreate File "/home/salma/gentoo/usr/lib64/python3.6/xml/parsers/expat.py", line 4, in from pyexpat import * ImportError: /home/salma/gentoo/usr/lib64/python3.6/lib-dynload/pyexpat.cpython-36m-x86_64-linux-gnu.so: undefined symbol: XML_SetHashSalt - ERROR: dev-util/meson-0.52.0::gentoo failed (compile phase):
- (no error message)
- Call stack:
- ebuild.sh, line 125: Called src_compile
- environment, line 2855: Called distutils-r1_src_compile
- environment, line 942: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
- environment, line 447: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
- environment, line 2388: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
- environment, line 1767: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
- environment, line 1765: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
- environment, line 649: Called distutils-r1_run_phase 'distutils-r1_python_compile'
- environment, line 933: Called distutils-r1_python_compile
- environment, line 801: Called esetup.py 'build' '-j' '3'
- environment, line 1311: Called die
- The specific snippet of code:
- "${@}" || die "${die_args[@]}";
- If you need support, post the output of
emerge --info '=dev-util/meson-0.52.0::gentoo'
,- the complete build log and the output of
emerge -pqv '=dev-util/meson-0.52.0::gentoo'
.- The complete build log is located at '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/temp/build.log'.
- The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/temp/environment'.
- Working directory: '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0'
- S: '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0'
Failed to emerge dev-util/meson-0.52.0, Log file:
'/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/temp/build.log'
Messages for package sci-libs/itk-5.0.1:
To tune ITK to make the best use of working memory you can set
ITK_COMPUTER_MEMORY_SIZE=XX
in make.conf, default is 1 (unit is GB)
Messages for package sys-fs/eudev-3.2.9:
As of 2013-01-29, eudev-3.2.9 provides the new interface renaming functionality,
as described in the URL below:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
This functionality is enabled BY DEFAULT because eudev has no means of synchronizing
between the default or user-modified choice of sys-fs/udev. If you wish to disable
this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules
exists: touch /etc/udev/rules.d/80-net-name-slot.rules
Messages for package media-fonts/liberation-fonts-2.00.5:
The following fontconfig configuration files have been installed:
60-liberation.conf
Use eselect fontconfig
to enable/disable them.
Messages for package dev-python/backports-1.0:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-python/olefile-0.46:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-python/mpmath-1.1.0:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-python/ptyprocess-0.5.2:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-python/functools32-3.2.3:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-python/subprocess32-3.5.4:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package media-fonts/stix-fonts-2.0.0:
The following fontconfig configuration files have been installed:
61-stix.conf
Use eselect fontconfig
to enable/disable them.
Messages for package dev-libs/boost-1.71.0:
Boost.Regex is extremely ABI sensitive. If you get errors such as
undefined reference to `boost::re_detail_107100::cpp_regex_traits_implementation
Then you need you need to recompile Boost and all its reverse dependencies
using the same toolchain. In general, every change of the C++ toolchain
requires a complete rebuild of the boost-dependent ecosystem.
See for instance https://bugs.gentoo.org/638138
Messages for package dev-python/six-1.13.0:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
Messages for package dev-util/meson-0.52.0:
Could not find a UTF-8 locale. This may trigger build failures in
some python packages. Please ensure that a UTF-8 locale is listed in
/etc/locale.gen and run locale-gen.
ERROR: dev-util/meson-0.52.0::gentoo failed (compile phase):
(no error message)
Call stack:
ebuild.sh, line 125: Called src_compile
environment, line 2855: Called distutils-r1_src_compile
environment, line 942: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
environment, line 447: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
environment, line 2388: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
environment, line 1767: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
environment, line 1765: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
environment, line 649: Called distutils-r1_run_phase 'distutils-r1_python_compile'
environment, line 933: Called distutils-r1_python_compile
environment, line 801: Called esetup.py 'build' '-j' '3'
environment, line 1311: Called die
The specific snippet of code:
"${@}" || die "${die_args[@]}";
If you need support, post the output of emerge --info '=dev-util/meson-0.52.0::gentoo'
,
the complete build log and the output of emerge -pqv '=dev-util/meson-0.52.0::gentoo'
.
The complete build log is located at '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/temp/build.log'.
The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/temp/environment'.
Working directory: '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0'
S: '/home/salma/gentoo/var/tmp/portage/dev-util/meson-0.52.0/work/meson-0.52.0'
GNU info directory index is up-to-date.
IMPORTANT: config file '/home/salma/gentoo/etc/hosts' needs updating.
See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
sections of the emerge man page to learn how to update config files.
Dear @salma1601 can you please paste the output of locale
?
Dear @TheChymera here is the output of locale
LANG= LC_CTYPE="POSIX" LC_NUMERIC="POSIX" LC_TIME="POSIX" LC_COLLATE="POSIX" LC_MONETARY="POSIX" LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL=
Please uncomment one of the lines in /etc/locale.gen
, e.g. en_US.UTF-8 UTF-8
, and then run:
locale-gen
source /etc/profile
If you encounter further issues, please consult the localization guide. In the end, locale
should return something like:
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC=en_US.utf8
LC_TIME=en_US.utf8
LC_COLLATE="en_US.utf8"
LC_MONETARY=en_US.utf8
LC_MESSAGES="en_US.utf8"
LC_PAPER=en_US.utf8
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT=en_US.utf8
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
Having said that, please enable the chymeric overlay as well (as described above). I am noticing now the newest SAMRI version in Gentoo Science is 0.2. That's pretty outdated, and we're running at 0.4 now.
Dear @TheChymera
I enabled the chymeric overlay but there is still some problem with dev-lang/python-3.6.9
. I am posting the whole traceback
make: *** [Makefile:603: sharedmods] Error 1
- ERROR: dev-lang/python-3.6.9::gentoo failed (compile phase):
- emake failed
- If you need support, post the output of
emerge --info '=dev-lang/python-3.6.9::gentoo'
,- the complete build log and the output of
emerge -pqv '=dev-lang/python-3.6.9::gentoo'
.- The complete build log is located at '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/build.log'.
- The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/environment'.
- Working directory: '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/work/Python-3.6.9'
- S: '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/work/Python-3.6.9'
Failed to emerge dev-lang/python-3.6.9, Log file:
'/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/build.log'
Messages for package sci-libs/itk-5.0.1:
To tune ITK to make the best use of working memory you can set
ITK_COMPUTER_MEMORY_SIZE=XX
in make.conf, default is 1 (unit is GB)
Messages for package sys-fs/eudev-3.2.9:
As of 2013-01-29, eudev-3.2.9 provides the new interface renaming functionality,
as described in the URL below:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
This functionality is enabled BY DEFAULT because eudev has no means of synchronizing
between the default or user-modified choice of sys-fs/udev. If you wish to disable
this new iface naming, please be sure that /etc/udev/rules.d/80-net-name-slot.rules
exists: touch /etc/udev/rules.d/80-net-name-slot.rules
Messages for package sys-apps/texinfo-6.7:
This package will overwrite one or more files that may belong to other
packages (see list below). You can use a command such as `portageq
owners /
` to identify the installed package that owns a file. If portageq reports that only one package owns a file then do
NOT file a bug report. A bug report is only useful if it identifies at
least two or more packages that are known to install the same file(s).
If a collision occurs and you can not explain where the file came from
then you should simply ignore the collision since there is not enough
information to determine if a real problem exists. Please do NOT file
a bug report at https://bugs.gentoo.org/ unless you report exactly
which two packages install the same file(s). See
https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
to solve the problem. And once again, please do NOT file a bug report
unless you have completely understood the above message.
Detected file collision(s):
/home/salma/gentoo/usr/bin/install-info
/home/salma/gentoo/usr/bin/makeinfo
Searching all installed packages for file collisions...
Press Ctrl-C to Stop
None of the installed packages claim the file(s).
Package 'sys-apps/texinfo-6.7' merged despite file collisions. If
necessary, refer to your elog messages for the whole content of the
above message.
Messages for package dev-lang/python-3.6.9:
ERROR: dev-lang/python-3.6.9::gentoo failed (compile phase):
emake failed
If you need support, post the output of
emerge --info '=dev-lang/python-3.6.9::gentoo'
,the complete build log and the output of
emerge -pqv '=dev-lang/python-3.6.9::gentoo'
.The complete build log is located at '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/build.log'.
The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/environment'.
Working directory: '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/work/Python-3.6.9'
S: '/home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/work/Python-3.6.9'
GNU info directory index is up-to-date.
IMPORTANT: config file '/home/salma/gentoo/etc/hosts' needs updating.
See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
sections of the emerge man page to learn how to update config files.
Dear @salma1601 , the relevant errors are contained within the /home/salma/gentoo/var/tmp/portage/dev-lang/python-3.6.9/temp/build.log
file. Can you please upload it here?
I see. This looks very much like a Gentoo Prefix system. Now that I re-read your original post, it appears that's what you meant by home. Sorry abut that, I thought you meant on your home computer :)
That shouldn't be an issue. We have transitioned all our systems to full Gentoo, but we had prefix until a few months ago, and it worked, and should in any case continue to work.
Can you try emerge --oneshot dev-libs/expat
and thereafter emerge -vaDNu world
?
@salma1601 what script did you use to set up the prefix installation?
@TheChymera I used the bootstrp-prefix.sh script https://gitweb.gentoo.org/repo/proj/prefix.git/plain/scripts/bootstrap-prefix.sh
@TheChymera I tried the emerge --oneshot dev-libs/expat
followed by emerge -vaDNu world
but there is still a failiure with the dev-lang
build.log
Hmmmmm... ok, so if you look at your error log this is related to a libexpat symbol. The issue seems to have cropped up a number of times (not on Gentoo, but on other distros), e.g. here: https://github.com/sqlmapproject/sqlmap/issues/2194 . I am assuming something from your user config is confusing the prefixed system.
Did you perhaps do some exotic edits to your user's LD_LIBRARY_PATH
? If so, could you temporarily disable them, re-log into your prefix, and try anew?
Sorry for the inconvenience, and for not having a straight answer as I did to the initial problems, but Prefix is a bit of a special case. At any rate, don't worry, we'll get this up and running!
dear @TheChymera , thank you for your support ! You are right, I have changed my LD_LIBRARY_PATH
in my .bashrc to match some software requirements. After unsetting it and retrying the install, things go better and the dev-lang
failiure is gone.
Now the emerge reached 114 of 166, failing for sci-libs/dcmtk-3.6.0::science
. Could it be because I already have dcmtk
installed on my machine ?
build.log
@salma1601 good, we're making progress :)
No, the dcmtk error is clearly a download issue. Can you reproduce this, or did your network maybe drop? I find it also curious that your system is trying to emerge =dcmtk-3.6.0
. This is a comparatively old version, the current version is considerably newer (you can browse all available Gentoo packages with eix
, to install it type emerge eix
):
chymera@darkhost ~ $ eix dcmtk -v
* sci-libs/dcmtk
Available versions: (~)3.6.0[1] (~)3.6.3 (~)3.6.4-r1
IUSE (all versions): doc png ssl tcpd +threads tiff xml zlib
Installed versions: Version: 3.6.4-r1
Date: 23:53:08 20/11/19
USE: png ssl tcpd threads tiff xml zlib -doc
DEPEND: ${RDEPEND} media-gfx/graphviz
RDEPEND: dev-libs/icu:0/65.1= virtual/jpeg:0 media-libs/libpng:* dev-libs/openssl:0/1.1= sys-apps/tcp-wrappers media-libs/tiff:0 dev-libs/libxml2:2 sys-libs/zlib
BDEPEND: dev-util/ninja >=dev-util/cmake-3.9.6
SRC_URI:
EAPI: 7
Best versions/slot: (~)3.6.4-r1
Homepage: https://dicom.offis.de/dcmtk.php.en
Find open bugs: https://bugs.gentoo.org/buglist.cgi?quicksearch=sci-libs%2Fdcmtk
Description: The DICOM Toolkit
License: OFFIS
[1] "science" /var/db/repos/science
What command are you using to get this error?
You are right! Actually it was a licence issue because I run the command echo 'ACCEPT_LICENSE="*"' >> /etc/portage/make.conf
only the first time. I ran it again, and the dcmtk
failiure is solved :)
Now the emerge fails at step 10 of 47 with sci-libs/nipy-0.4.2::science
, appearently there is an issue with nibabel
?
build.log
This is strange... nipy is complaining that it cannot find nibabel, but nibabel is listed as one of its dependencies, and should thus be already present. What does eix nibabel
say?
Not least of all, echo 'ACCEPT_LICENSE="*"' >> /etc/portage/make.conf
was part of the instructions I gave you before I realized this was Prefix. It should be echo 'ACCEPT_LICENSE="*"' >> /home/salma/gentoo/etc/portage/make.conf
unless prefix auto-assigns /
to /home/salma/gentoo
, which I somewhat doubt and can't check, since I don't have a Prefix machine. Could you just look at the file and see if the license definition is in there?
@TheChymera licence is OK and this is the output of eix nibabel
[I] sci-libs/nibabel
Available versions: 2.0.1[1] 2.1.0[1] 2.3.0[1] 2.3.1[1] 2.5.1[1] 2.5.1[2] **9999*l[1] {dicom doc test PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"}
Installed versions: 2.5.1[2](10:56:22 PM 12/05/2019)(-dicom -doc -test PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7")
Homepage: http://nipy.org/nibabel/
Description: Access a cacophony of neuro-imaging file formats
[1] "science" /home/salma/gentoo/var/db/repos/science
[2] "chymeric" /home/salma/gentoo/var/db/repos/chymeric
so you have the newest version of nibabel already installed. Strange that nipy isn't finding it. Can you try importing it in the Python interpreter?
Yes I do have nibabel because I already use it with other nipy libraries. Here is the output of python -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
2.5.1 /home/salma/miniconda3/lib/python3.7/site-packages/nibabel/init.py
@salma1601 but I assume this is outside of Prefix? So the way Prefix works, is it creates its own system inside of /home/salma/gentoo
. It's basically like a container but without the device mapping overhead.
From the output you pasted, this looks like nibabel from the parent system installation. Prefix can obviously not use this, because otherwise it would lead to significant confusion as to which packages are being used. If you get this output running python -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
inside Prefix, it means that your PYTHONPATH
is similarly edited as LD_LIBRARY_PATH
was before. So maybe try to clean that up?
OK I understand better. Actually I have miniconda3 binaries added to my PATH
in my ~/.bashrc
. So I unset my PYTHONPATH
removed from PATH
all paths pointing outside gentoo directory and rerun the emerge but it is still failing at the same point
build.log
and the output of python -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
is now
2.5.1 /home/salma/gentoo/usr/lib64/python3.6/site-packages/nibabel/init.py
@salma1601 hm.... yes, looks like it's properly accessible now. The error message seems to come from the package's setup.py
and not from Portage, meaning that it's trying to check for the package itself, in excess of what Portage does. And somehow it's not managing to...
Maybe this is Python-version contingent (though, again, Portage should be handling all of this automatically, and based on your eix
output, it definitely has). At any rate, try:
python2.7 -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
python3.6 -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
And please post the output of:
eselect python list
@TheChymera here are the outputs
python2.7 -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
Traceback (most recent call last): File "
", line 1, in File "/home/salma/gentoo/usr/lib64/python2.7/site-packages/nibabel/init.py", line 62, in from . import analyze as ana File "/home/salma/gentoo/usr/lib64/python2.7/site-packages/nibabel/analyze.py", line 87, in from .volumeutils import (native_code, swapped_code, make_dt_codes, File "/home/salma/gentoo/usr/lib64/python2.7/site-packages/nibabel/volumeutils.py", line 23, in from .openers import Opener, BZ2File File "/home/salma/gentoo/usr/lib64/python2.7/site-packages/nibabel/openers.py", line 14, in from bz2file import BZ2File ImportError: No module named bz2file
python3.6 -c "import nibabel; print(nibabel.__version__, nibabel.__file__)"
2.5.1 /home/salma/gentoo/usr/lib64/python3.6/site-packages/nibabel/init.py
eselect python list
Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback)
@salma1601 I see, something is quite obviously broken with the Python 2.7 installation of nibabel. It appears there is an extra runtime dependency, specific for python2.7, which I have failed to document.
please check with eix bz2file
whether it is already installed, if not, emerge it with emerge -v1 bz2file
. This will emerge it only once but not add it to the world package set, this is useful because you only want to get it as a quick fix. If this solves the issue, let me know, and I will add it to the dependency list for all users to benefit from (and to act as a permanent fix).
Dear @salma1601 as far as I can tell, this is not because of your own dcmtk, but because prefix detected the package wanted to install outside of the prefix. This is most likely due to the developer not having tested the package for prefix. We try to be careful about this sort of things, but as I said, Prefix is a bit of an edge case, and most developers do not use this functionality on their own machines.
A quick search indicates that the guilty developer is.... me :-/ https://github.com/gentoo/gentoo/commit/3494cfeb45b8fefd8a39d3ffdbde30a5423a3740
I am working on updating this package, so it should be back in order soon.
@salma1601 I believe I have fixed it. Try running eix-sync && emerge -vaDNu world
.
@TheChymera I think you did fix it! Now failing for ANTs :) build.log
It seems to nit find ITK. can you paste the output of: eix itk
and equery f itk
?
@TheChymera the output of eix itk
is
* dev-python/nuitka
Available versions: 0.6.0.6 0.6.2 0.6.4 0.6.5 {PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"}
Homepage: https://www.nuitka.net
Description: Python to native compiler
* dev-tcltk/itk
Available versions: 3.4.1^t 4.0.0 4.0.1 4.1.0^t {test}
Homepage: http://incrtcl.sourceforge.net/
Description: Object Oriented Enhancements for Tcl/Tk
[I] sci-libs/itk [1]
Available versions: 5.0.1^p {debug doc examples fftw python review test vtkglue PYTHON_SINGLE_TARGET="python2_7 python3_5 python3_6 python3_7" PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"}
Installed versions: 5.0.1^p(07:02:12 AM 12/08/2019)(-debug -doc -examples -fftw -python -review -test -vtkglue PYTHON_SINGLE_TARGET="python3_6 -python2_7 -python3_5 -python3_7" PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7")
Homepage: http://www.itk.org
Description: NLM Insight Segmentation and Registration Toolkit
* www-apache/mpm_itk
Available versions: 2.4.7_p4-r1 {KERNEL="linux"}
Homepage: http://mpm-itk.sesse.net/
Description: Run virtual hosts under separate users/groups
[1] "science" /home/salma/gentoo/var/db/repos/science
Found 4 matches
and the output of equery f itk
is here
Ok, I submitted a fix, you can try again :)
@salma1601 apologies, you need to get the fix first (via eix-sync
).
it is still failing for ANTs, but apparently for another reason build.log
@TheChymera any progress on this ?
@salma1601 sorry, I missed your previous reply. Hmmm....
what does
ls home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/usr/lib64/
ls home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/usr/
ls home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/
say?
@TheChymera The folder usr
is not directly in /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image
salma@salma-Latitude-E7450 ~/gentoo $ ls /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/usr
ls: cannot access '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/usr': No such file or directory
It is located in /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/home/salma/gentoo/
. Here are the paths
salma@salma-Latitude-E7450 ~/gentoo $ ls /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/home/salma/gentoo/usr/lib64/
ants
salma@salma-Latitude-E7450 ~/gentoo $ ls /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/home/salma/gentoo/usr/
bin lib lib64 share
salma@salma-Latitude-E7450 ~/gentoo $ ls /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/image/home/salma/gentoo/
usr
Hm... ok, this is a bit of stabbing in the dark on my part since I don't have a prefix, but I think I might have figured it out. Try:
emerge --sync chymeric # this specifically syncs the Chymeric Overlay where I test fixes
emerge -v ants::chymeric # this specifically compiles ANTS according to the instructions from that overlay
Oh, this is strange. The error you got previously was because the install command was confused about the directories. The error you get now seems to indicate a dependency is missing. Did you change anything else? Does emerge -v ants::science
still take you to where it took you before?
I restarted my laptop meanwhile, so I restarted the prefix and executed source ~/gentoo/etc/bash/bashrc
.
emerge -v ants::science
output is
* ERROR: sci-biology/ants-2.3.1_p20191013::science failed (configure phase):
* cmake failed
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 2652: Called cmake-utils_src_configure
* environment, line 1123: Called die
* The specific snippet of code:
* "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
*
* If you need support, post the output of `emerge --info '=sci-biology/ants-2.3.1_p20191013::science'`,
* the complete build log and the output of `emerge -pqv '=sci-biology/ants-2.3.1_p20191013::science'`.
* The complete build log is located at '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/build.log'.
* The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/environment'.
* Working directory: '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/work/ants-2.3.1_p20191013_build'
* S: '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/work/ants-2.3.1_p20191013'
>>> Failed to emerge sci-biology/ants-2.3.1_p20191013, Log file:
>>> '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/build.log'
* Messages for package sci-biology/ants-2.3.1_p20191013:
* ERROR: sci-biology/ants-2.3.1_p20191013::science failed (configure phase):
* cmake failed
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 2652: Called cmake-utils_src_configure
* environment, line 1123: Called die
* The specific snippet of code:
* "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
*
* If you need support, post the output of `emerge --info '=sci-biology/ants-2.3.1_p20191013::science'`,
* the complete build log and the output of `emerge -pqv '=sci-biology/ants-2.3.1_p20191013::science'`.
* The complete build log is located at '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/build.log'.
* The ebuild environment file is located at '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/environment'.
* Working directory: '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/work/ants-2.3.1_p20191013_build'
* S: '/home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/work/ants-2.3.1_p20191013'
@salma1601 as usual, could you please paste the actual build log (path is listed on the fourth line from the bottom in the output you just pasted: /home/salma/gentoo/var/tmp/portage/sci-biology/ants-2.3.1_p20191013/temp/build.log
)
Ok, so it seems it's looking for GCC on your parent system: /home/salma/mcr_matlab2018b_test/v95/sys/os/glnxa64/libstdc++.so.6
Are you sure you don't have any GCC-related environment variable inherited from the parent system?
In addition, where did you find the instructions to run source ~/gentoo/etc/bash/bashrc
? Just curious since to my knowledge this isn't good advice. Run source ~/gentoo/etc/profile
(or, more unambiguously PREFIX=$(python -c "import portage; print(portage.root)"); source ${PREFIX}etc/profile
).
Dear SAMRI experts,
I am trying to install SAMRI. I installed gentoo in my home, installed the overlay science in
/home/salma/gentoo/var/db/repos
and tried to emerge samri but I am getting the following errorThe following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details)
required by sci-libs/scipy-1.1.0::gentoo
required by dev-python/bottleneck-1.2.1::gentoo
required by dev-python/pandas-0.24.2::gentoo[-minimal]
required by dev-python/seaborn-0.9.0::gentoo
required by sci-biology/samri-0.2::science
required by samri (argument)
=dev-python/numpy-1.16.5 lapack
required by sci-libs/nipype-1.1.1-r1::science[python_targets_python2_7]
required by sci-biology/samri-0.2::science
required by samri (argument)
The following license changes are necessary to proceed: (see "package.license" in the portage(5) man page for more details)
required by sci-biology/samri-0.2::science
required by samri (argument)
Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). Carefully examine the list of proposed changes, paying special attention to mask or keyword changes that may expose experimental or unstable packages.
!!! The following updates are masked by LICENSE changes:
For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
emerge: there are no ebuilds built with USE flags to satisfy "dev-python/numpy[lapack,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]". !!! One of the following packages is required to complete your request: