Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 06:30

    Biswa96 on master

    qbittorrent: update to 4.4.3 (compare)

  • 06:29

    Biswa96 on master

    hugo: update to 0.99.1 (compare)

  • 06:24

    Biswa96 on master

    hexyl: update to 0.10.0 (compare)

  • 06:12
    MehdiChinoune commented #228
  • 06:07
    windelbouwman commented #228
  • 05:55
    shithappens2016 commented #11711
  • 05:45
    shithappens2016 commented #11711
  • 05:29
    Biswa96 commented #11711
  • 05:28
    revelator commented #11710
  • 05:24
    shithappens2016 commented #11711
  • 05:23
    shithappens2016 commented #11711
  • 05:20
    shithappens2016 commented #11711
  • May 23 23:42
    filnet commented #11700
  • May 23 23:29
    filnet synchronize #11700
  • May 23 23:25
    filnet synchronize #11700
  • May 23 22:39
    cyrilarnould commented #11676
  • May 23 22:06
  • May 23 21:54
    revelator commented #11628
  • May 23 21:29
    Dasperal commented #11712
  • May 23 20:12
    MehdiChinoune commented #11712
Biswapriyo Nath
@Biswa96
Just curious, in which commit it was kicked out?
fulcobohle
@fulcobohle
on the news page it is mentioned that Ada and Objc are no longer supported: https://www.msys2.org/news/
I build software using objective-c on Windows...
Mateusz Mikuła
@mati865
@Biswa96 IIRC during one of GCC upgrades since it didn't build.
Biswapriyo Nath
@Biswa96
But there is a package mingw-w64-x86_64-gcc-objc?
Mateusz Mikuła
@mati865
Oh, it was readded in msys2/MINGW-packages@7e59389
fulcobohle
@fulcobohle
I got here because of a memory leak in bzip2, this forced me to update.
So it is back on track ?
David Macek
@elieux
Heh, it says "unsupported until further notice" and we didn't issues any further notices.
But AFAIK it's back in.
fulcobohle
@fulcobohle
Now that I am here, do you need my help supporting msys2 in the future ? If yes where do I start...
David Macek
@elieux
Depends on your proficiencies.
fulcobohle
@fulcobohle
I am of the generation Bill Gates, build my own computer before you could buy any, wrote an operating system for it. The only difference is my bank account :-(
David Macek
@elieux
:D
We have a lot of tickets, so if you can debug and/or patch stuff, that'll be definitely appreciated.
fulcobohle
@fulcobohle
I have 40 years experience in c
David Macek
@elieux
You can try picking something from https://github.com/msys2/MINGW-packages/issues.
Alternatively someone else here could have something to work on.
... which would have the upside of having someone know the context.
fulcobohle
@fulcobohle
First I have to download the software, do I do that on Windows or on Linux ? Can I build msys2 on msys2
What is a typical setup for development ?
Christoph Reiter
@lazka
Development happens on Windows only. But experience with Linux helps a lot.
David Macek
@elieux
If you want to try one of those mingw-packages issues, you download and install MSYS2 on Windows, update and install packages (see homepage), download the mingw-packages repository and use makepkg-mingw to build (see Building packages).
Unai Martinez-Corral
@umarcor

@fulcobohle I found that some packages are not buildable at the moment. For example mingw-w64-graphviz or mingw-w64-gtkwave (which sometimes works sometimes fails due to some Gtk header). Those are rather old school (but still used) tools which you might have fun looking at. Steps for testing are the following:

# Update MSYS2
pacman -Syu

# Install minimal build tools
pacman -S git base-devel mingw-w64-x86_64-toolchain

# Get package recipes
git clone https://github.com/msys2/MINGW-packages
cd MINGW-packages

# Build the package you want to test
cd mingw-w64-graphviz
MINGW_INSTALLS=mingw64 makepkg-mingw --noconfirm --noprogressbar -sCLf --nocheck

You can remove --nocheck for having the check function of recipe executed after the tool is built. You can also remove MINGW_INSTALLS for having the package built for i686 and x86_64.

That same procedure works for building any package. Just change the directory.

The specific issue with gtkwave is D:/a/_temp/msys/msys64/mingw64/include/gtk-2.0/gtk/gtktooltips.h:73:3: internal compiler error: Segmentation fault, which happens arbitrarily on either MINGW32 or MINGW64.
With graphviz, the error is D:/a/_temp/msys/msys64/mingw64/include/gtk-2.0/gtk/gtkitemfactory.h:49:10: internal compiler error: Segmentation fault.
Mateusz Mikuła
@mati865
@umarcor can you obtain backtrace using gdb or lldb?
Unai Martinez-Corral
@umarcor
Hi @mati865, I would need to be instructed about how to do so. Both of those recipes were written by someone else. I did update gtkwave's recipe a few times, but I did not even read graphviz's (just executed it in CI https://github.com/hdl/MINGW-packages/blob/main/.github/workflows/build.yml).
I am more familiar with the problem in gtkwave since I have been looking at it for several months. As I said, build success/failure is aparently random. Just running the build several times leads to an eventual success.
Anyway, I'm willing to test it locally and get whatever feedback you suggest me to try.
jeremyd2019
@jeremyd2019
I personally had a lot of fun trying to debug crashes in gcc
Mateusz Mikuła
@mati865
It's quite difficult to debug compiler crashes.
jeremyd2019
@jeremyd2019
I started out using cv2pdb and windbg and that worked pretty well (based on my existing experience with windbg), but I was also able to use gdb
This is why I came up with msys2-runtime/cygwin upstreamed patch to allow windows just-in-time debugger to be invoked when a native program crashes when launched from a msys2/cygwin process
regarding the libbacktrace message, I have always gotten that too. would have been helpful if it did work
oh, and you would probably need to rebuild gcc with options debug !strip (and maybe other libraries if they wind up being involved, like my adventures with gmp)
Christoph Reiter
@lazka
I also just hit "internal compiler error"
jeremyd2019
@jeremyd2019
ouch
Christoph Reiter
@lazka
but second time worked :)
eventual compilability
jeremyd2019
@jeremyd2019
are there any known issues with using --log with makepkg (specifically makepkg-mingw)?
Mateusz Mikuła
@mati865
lots of text files :P
jeremyd2019
@jeremyd2019
I was reliably getting the crash in clang (msys2/CLANG-packages#3) building gettext, but just tried without --log and it made it through ok. I've also been seeing flakiness with makepkg itself, either hanging, exiting without message, or exiting reporting signal 13 (SIGPIPE), generally when transitioning between 'phases'
Mateusz Mikuła
@mati865
maybe it took too much memory or IO?
Christopher Degawa
@1480c1
I've had issues with tee itself hanging
Unai Martinez-Corral
@umarcor

I've had issues with tee itself hanging

I've had issues with tee hanging when I terminate a call to makepkg-mingw with Ctrl+C.

fulcobohle
@fulcobohle
@umacor
First I need to setup a new virtual machine, then I will look into mingw-w64-graphviz and mingw-w64-gtkwave
fulcobohle
@fulcobohle
@umarcor sorry for the typo
David Macek
@elieux
Yeah, tee got stuck for me too a few times.
Unai Martinez-Corral
@umarcor
@fulcobohle, no worries and no rush. I told it because you asked for ideas and just for illustrating the process.