Reputation: 271
I have a problem with installing gnucobol 2.2. I get an error message telling me there's no c compiler found. I run windows10 on my laptop
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... no
checking whether make supports nested variables... no
checking whether CFLAGS can be modified... yes
checking for gcc... no
checking for xlc... no
checking for cc... no
configure: error: in `/cygdrive/c/gnucobol-2.2-rc':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
can someone please help me with this problem? thank you :)
Upvotes: 0
Views: 1957
Reputation: 7297
Cygwin has its own package manager: setup-x86_64.exe.
This is a GUI application where you'd enable the contents of the base-essentials meta package, at least "gcc" and "make".
To build GnuCOBOL from source you'll need to add additional packages, see GnuCOBOL's DEPENDENCIES file.
IF you'd want to install without the GUI, then as an alternative to apt-get
you could use cyg-get
. Instead of "sudo", which doesn't exist you may need to start Cygwin as Administrator, if you didn't do a user-install.
Apart from this question: as this question shows that you aren't using Cygwin for development in general and likely just want to use it on GnuCOBOL: have a look at the official MinGW packages, this is just a download, extract and double click to "set_env.cmd", then you're ready to go.
Upvotes: 1
Reputation: 479
Whilst not directly related to the "./configure" question, a general "easy" answer to "installing gnucobol on windows10" might be:
https://community.chocolatey.org/packages/gnucobol
This doesn't work at the moment due to an issue with the packaging, but generally speaking is likely the easiest "just install" option on native Windows
WSL is "Windows Subsystem for Linux". See https://learn.microsoft.com/en-us/windows/wsl/install . The drawback of this approach is that if you're using gnucobol to create objects, libraries or executables (as opposed to just C code) then you'll get Linux objects, libraries or executables, which likely isn't what you want on Windows. However, for just getting access to the environment, it's likely the fastest way there.
Upvotes: 3