Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker image building failed #36

Open
russian-developer opened this issue Mar 13, 2023 · 3 comments
Open

Docker image building failed #36

russian-developer opened this issue Mar 13, 2023 · 3 comments

Comments

@russian-developer
Copy link

russian-developer commented Mar 13, 2023

Checkout code from the repo and try to build got failed.

Step 21/27 : RUN cd /.swig && ./autogen.sh && ./configure && make && make install
 ---> Running in 3be5e7dfd9b6
+ test -d Tools/config
+ aclocal -I Tools/config
+ autoheader
+ automake --add-missing --copy --force-missing
configure.ac:23: installing 'Tools/config/compile'
configure.ac:11: installing 'Tools/config/config.guess'
configure.ac:11: installing 'Tools/config/config.sub'
configure.ac:12: installing 'Tools/config/install-sh'
configure.ac:12: installing 'Tools/config/missing'
Source/Makefile.am: installing 'Tools/config/depcomp'
configure.ac: installing 'Tools/config/ylwrap'
+ autoconf
+ cd CCache
+ autoreconf
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking maximum warning verbosity option... -Wall -W -pedantic for C++ -Wall -W -pedantic for C
checking CFLAGS to compile SWIG executable... -g -O2 -Wall -W -pedantic
checking CXXFLAGS to compile SWIG executable... -g -O2 -Wall -W -pedantic
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether to enable PCRE2 support... yes
checking whether to use local PCRE2... no
checking for a sed that does not truncate output... /bin/sed
checking for pcre2-config... no
configure: error: in `/.swig':
configure: error: 
        Cannot find pcre2-config script from PCRE2 (Perl Compatible Regular Expressions)
        library package. This dependency is needed for configure to complete,
        Either:
        - Install the PCRE2 developer package on your system (preferred approach).
        - Download the PCRE2 source tarball, build and install on your system
          as you would for any package built from source distribution.
        - Use the Tools/pcre-build.sh script to build PCRE2 just for SWIG to statically
          link against. Run 'Tools/pcre-build.sh --help' for instructions.
          (quite easy and does not require privileges to install PCRE2 on your system)
        - Use configure --without-pcre to disable regular expressions support in SWIG
          (not recommended).
See `config.log' for more details
The command '/bin/sh -c cd /.swig && ./autogen.sh && ./configure && make && make install' returned a non-zero code: 1```
@kovacsur
Copy link

Did you try any of the 4 solutions listed in the error message?

@russian-developer
Copy link
Author

@kovacsur I guess we should have an image on docker hub or INSTALL.md with fully explanation and a list of dependency.

@russian-developer
Copy link
Author

And yes, I tried. In deep, I had more errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants