Add a New Comment (Rich Markup)
Thanks for the quick reply Mohammad! Yes, I did go with the --host-cc option, and the project was configured without any errors! I also moved forward with building the Python wheels, without modifying any dependencies or the high-level.mk for now, and the wheel had very less amount of dependencies than before! Now, I'm trying by modifying the high-level.mk file, where I move all the .so files of the dependencies of Gnuastro out of the /build/software/installed /lib directory, so that the libgnuastro.so file is built statically. == Reproduce the Problem == 1. Clone the https://gitlab.com/makhlaghi/gnuastro-in-maneage-static repo. 2. Have docker setup in your environment. 3. Follow the steps in https://gitlab.com/makhlaghi/gnuastro-in-maneage-static#only-software-environment-in-the-docker-image 4. Except in Step 3, change line 1 in Dockerfile to
FROM quay.io/pypa/manylinux2014_x86_64:latest
5. The error appears after running step 10. I've also attached a longer .log file of the output of ./project configure. (file #53653)
Thanks for sharing this problem Jash. Unfortunately the log file doesn't contain the actual error! It must have been caused by lines above the part you sent. Do you still have the terminal open? If not, can you post the name of the Docker image you used so I can try it? Until then, to get things going, you can use '--host-cc' (as the suggestion at the end of the log says). With this option, Maneage will not build GCC, and will use the host GCC and C++ Standard library for the high-level software. It shouldn't affect Gnuastro's library because Gnuastro (or its dependencies) don't link with the C++ library.
I've been working on building a Python implementation of Gnuastro. This required me to use a manylinux2014_x86_64 based docker image, which uses CentOS 7. I chose gnuastro-in-maneage-static maneage project to build gnuastro statically, so that the Python package extension modules would only have to link to one shared lib, and thus only that one library(libgnuastro.so) is included in the Python distribution wheel. Look at auditwheel for more info. However while following the steps to Build only a software env in the docker the build failed with the following error while building GCC. I've included as much as my terminals max output allowed in the attached log file. Any help would be great!
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 2 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.11