How to Install and Uninstall mingw32-libgcc_s_sjlj1 Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "mingw32-libgcc_s_sjlj1" package

Here is a brief guide to show you how to install mingw32-libgcc_s_sjlj1 on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                mingw32-libgcc_s_sjlj1
            
                    
    
    Copied

2. Uninstall "mingw32-libgcc_s_sjlj1" package

This guide covers the steps necessary to uninstall mingw32-libgcc_s_sjlj1 on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                mingw32-libgcc_s_sjlj1
            
                    
    
    Copied

3. Information about the mingw32-libgcc_s_sjlj1 package on openSuSE Tumbleweed

Information for package mingw32-libgcc_s_sjlj1:
-----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : mingw32-libgcc_s_sjlj1
Version : 13.2.0-2.1
Arch : noarch
Vendor : openSUSE
Installed Size : 132.5 KiB
Installed : No
Status : not installed
Source package : mingw32-gcc-13.2.0-2.1.src
Upstream URL : http://www.mingw.org/
Summary : MinGW Windows compiler for C shared libraries
Description :
MinGW Windows compiler for C shared libraries
This libgcc build uses SJLJ, a method for exception handling based on
setjmp/longjmp. SJLJ-based EH is much slower than DWARF-2 EH,
penalizing even normal execution when no exceptions are thrown, but
can work across code that has not been compiled with GCC or that does
not have call-stack unwinding information.
[The DWARF-2 EH implementation for Windows is not at all designed to
work under 64-bit Windows applications. In Win32 mode, the exception
unwind handler cannot propagate through non-DW2 aware code, which
means that any exception going through any non-DW2-aware "foreign
frame" code will fail, including Windows system DLLs and DLLs built
with Visual Studio. DWARF-2 unwinding code in GCC inspects the x86
unwinding assembly and is unable to proceed without other DWARF-2
unwind information.]