Installing error with GLIBC_2.15

[Weiqi Ji]

Hi,

I got the problem when installing Cantera via conda in a Linux HPC (Tianhe-2 in China). It comes out the issue of

ImportError: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /HOME/thu_zhyren_1/anaconda3/lib/python3.5/site-packages/cantera/_cantera.cpython-35m-x86_64-linux-gnu.so)

The issue is due to that the GLIBC in my system doesn't contain the version of 2.15. After I consulted the system administrator, they suggest me to install a Cantera which doesn't require the GLIBC at the version of 2.15.

Does anyone get the same problem? Or suggest a version of Cantera that doesn't require the GLIBC at the version of 2.15.

Thanks in advance

Weiqi

[Bryan W. Weber]

Weiqi,

We build the conda packages on Travis-CI, which apparently has GLIBC 2.15 installed, where as the libc on your system doesn't contain this. I'd recommend building your own conda package, or building from source. To build a package for 2.3.0, do the following

git clone https://github.com/Cantera/conda-recipes

git checkout 2.3

conda build cantera [--python=#.#]

conda install --use-local cantera

The [--python=#.#] represents an optional argument that you can pass to set the Python version that the package will be built for, if its different than the root environment's Python version. For more general compilation instructions, you can look at the online documentation: http://cantera.github.io/docs/sphinx/html/compiling/index.html

Best,

Bryan

[Ray Speth]

Weiqi,

Based on the age of the version of GLIBC installed on your system, you should first check to make sure you have a recent-enough version of GCC/G++ installed. Cantera 2.3.0 requires GCC 4.6 or newer. If you don't have a sufficiently recent compiler available, you won't be able to compile or use the current version of Cantera.

Regards,

Ray

[ananda sreenivas]

On my linux I am trying to install cantera through conda. I am getting the same error. I have Redhat 6.7. So. unless I upgrade my linux, I cant have GCC 4.6.  

can CANTERA 2.2.1 installable with lower versions of GCC?  

Again,

my network is behind the firewall. Not possible to access repositories. If there is web location, I can use round about to download them and place them in my system and install.

Between, thanks to Bryan, at least I have the 2.3 running on my windows.  

Thanks

Ananda

[Bryan W. Weber]

Ananda,

I don't know about the requirements for 2.2.1, but depending on the problems you're solving, 2.3.0 has a lot of improvements. So I'd recommend you use 2.3.0 if at all possible.

This is entirely unsupported, I don't know if its good advice, and I haven't tried it so I can't offer any support beyond links, but you might be able to install GCC 4.8 on your computer. CERN provides a download of the developer-toolset package which has GCC 4.8: http://linux.web.cern.ch/linux/devtoolset/#install (or if you have a subscription, you can get the RHEL official developer toolset: https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/2/html/User_Guide/sect-Red_Hat_Developer_Toolset-Install.html) If you download the RPM for that onto another computer (https://access.redhat.com/solutions/10154) and move it to the firewalled computer, then you can install the local file: http://unix.stackexchange.com/questions/183063/local-installation-of-rpms-using-yum (see the second answer). Once its installed, though I don't know how to activate it or ensure that you pick up the correct libraries when running Cantera.

Again, I haven't tried that, and I don't have an RHEL machine on which to try it, so you're going to be on your own. Sorry I can't be more help! Questions specifically about installing GCC 4.8 on RHEL should probably be directed to a forum with some folks who have more experience with RHEL, though, as I don't know how much RHEL experience we have on the forum here.

Best,

Bryan

[Nick Curtis]

Speaking from experience with RHEL, the dev-toolset is a bit tricky to get the paths working correctly (passing them to SCons etc.)
It is doable, but I would recommend instead building the new GCC from source (which isn't trivial, but not too bad either) giving you much more control over paths etc.

Nick

[ananda sreenivas]

Bryan and Nick,

My original attempt was to install 2.3. But it failed with same error. Hoping an older canter version could be compatible with and older gcc, I attempted installing 2.2.1. But if 2.3 is installable with some package, I am eager to try. In fact the windows was done in a similar way through Bryan's suggestions.

Ananda

Sent from my iPhone

--
You received this message because you are subscribed to a topic in the Google Groups "Cantera Users' Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cantera-users/LlmDCatVXDo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cantera-user...@googlegroups.com.
To post to this group, send email to canter...@googlegroups.com.
Visit this group at https://groups.google.com/group/cantera-users.
For more options, visit https://groups.google.com/d/optout.

[Bryan W. Weber]

Ananda,

To be clear, you will have to either install (as I suggested) or build (as Nick suggested) the new version of GCC then build and install Cantera 2.3.0. As far as I can recall, the only packages for Cantera are conda packages and Ubuntu deb packages, we don't build RPM packages for Red Hat/Fedora etc.

Once you have the new GCC installed, you can follow the instructions I gave to Weiqi in my first response to this thread to build a conda package, or follow the compiling instructions on cantera.org to build and install regularly. But you have to be careful to specify the proper version of the GCC compiler in the build stage.

Regards,
Bryan

On Friday, February 10, 2017 at 11:05:46 AM UTC-5, ananda sreenivas wrote:

Bryan and Nick,

My original attempt was to install 2.3. But it failed with same error. Hoping an older canter version could be compatible with and older gcc, I attempted installing 2.2.1. But if 2.3 is installable with some package, I am eager to try. In fact the windows was done in a similar way through Bryan's suggestions.

Ananda

Sent from my iPhone

To unsubscribe from this group and all its topics, send an email to cantera-users+unsubscribe@googlegroups.com.

[ananda sreenivas]

I have copied the conda recipies on to my linux machine. 

when I try " conda build --python=2.7 cantera"   . I see the following error .. 

usage: conda [-h] [-V] command ...

conda: error: argument command: invalid choice: '/root/anaconda2/bin/conda' (choose from u'info', u'help', u'list', u'search', u'create', u'install', u'update', u'upgrade', u'remove', u'uninstall', u'config', u'clean', u'package')

It is refusing to build..  what am I missing .. 

Thanks

Ananda

To unsubscribe from this group and all its topics, send an email to cantera-user...@googlegroups.com.

[Bryan W. Weber]

You have to install the conda-build package.

Regards,

Bryan

[ananda sreenivas]

I guess I get stuck at every next step. 

I could install the conda build package, but it is now looking for filelock.  "ImportError: No module named filelock" .. Could you kindly let me know how to resolve this. I saw the file lock error's on other forums. But, not sure how to apply it in conda environment. 

Thanks

Ananda

[Bryan W. Weber]

The ImportError means the package is missing. Did you try

conda install filelock

?

Regards,

Bryan

[Bryan W. Weber]

I just remembered you're installing this on a firewalled machine. Look here: https://github.com/conda/conda-build/blob/master/conda.recipe/meta.yaml#L24 to see all of the runtime dependencies. You will have to install packages for each one of those.

Regards,
Bryan

[ananda sreenivas]

It will be fun :-)

Thanks for you patience 

Ananda

Sent from my iPhone

[thomas...@boostheat.com]

Hello,

I have the same RHEL version and you can have GCC 5.2 from developper toolset as already said.

And for information Anaconda also have recipes for gcc ! 

conda install -c anaconda gcc 

Regards,

Thomas 

Avis : Ce message et toute pièce jointe sont la propriété de boostHEAT et sont destinés seulement aux personnes ou à l'entité à qui ce message est adressé. Les informations contenues dans ce message peuvent avoir un caractère confidentiel et sa divulgation ou reproduction est strictement interdite. Si vous avez reçu ce message par erreur, veuillez le retourner immédiatement à l'expéditeur par courriel et le détruire. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie.

 Notice: This e-mail message and any attachment are the property of boostHEAT and are intended solely for the use of the named recipient(s) or entity to whom this message is addressed. The information contained therein may be confidential or privileged, and its disclosure or reproduction is strictly prohibited. If you have received this message in error, please return it immediately to its sender at the above e-mail address and destroy it. If you are not the intended recipient you are not allowed to use, copy or disclose the content or attachments of this message in whole or in part.