#GNUCOBOL Stops working after pacman -Syu

1 messages · Page 1 of 1 (latest)

pine wind
#

After downloading MSYS2 (https://www.msys2.org/) to a brand new Windows 11 computer, install it, update it, then install GNUCobol using pacman, cobc, after pressing enter, just comes back with another prompt. No message, no nothing. Here's what I do to recreate the problem:

  1. Download and install MSYS2 from https://www.msys2.org/
  2. Start MSYS2 MSYS
  3. Type pacman -Syu
  4. Type pacman -Su
  5. Type pacman -S mingw-w64-x86_64-gnucobol
  • Not that install works fine and all dependencies are installed
  1. Close MSYS2 MSYS and open MSYS2 MINGW64
  2. Type: cobc
  • All that is displayed is another terminal prompt
  1. If I type cobc --version
  • All that is displayed is another terminal prompt

How to fix the problem

  1. Using Add/Remove programs, remove MSYS2
  2. Delete the MSYS64 directory from the C: drive
  3. Reinstall MSYS2
  4. Start MSYS2 MSYS and type: pacman -S mingw-w64-x86_64-gnucobol
  • Note that I did zero updates or did I install anything else
  1. Close MSYS2 MSYS, open MSYS2 MINGW64
  2. Type: cobc
  • Get the appropriat configuration file missing issue (good)
  1. Type: cobc --version
  • Get the version (3.2 rc2) displayed just fine

Note: If I do a pacman -Syu and pacman -Su after this, cobc stops working again

I have notified the GNUCOBOL team as well.

This is new behavior. I've never had this happen before. Any ideas? Thanks everyone!

lunar walrus
#

A fix is coming, an update from rc2 to stable release didn't go well. It's still stuck in 3.2-rc2

pine wind
lunar walrus
#

It's in staging repo, will be deployed soon.

pine wind
#

You're the best!

void shuttle
#

It should work now