Hi Rob, No problems for me because I recompiled it to be statically linked.
On Wed, May 22, 2024 at 8:01 PM Rob CJ <[email protected]> wrote: > Hi Vasi, > > I had problems with GLIBC version 2.29. In order to solve that I > recompiled the JAL compiler with an older version of gcc and that solved > that issue. > > I can have a look a linking it statically. Are you - or other JAL users - > experiencing problems with the current version (2.5r8) of the JAL compiler? > > Kind regards, > > Rob > > ------------------------------ > *Van:* [email protected] <[email protected]> namens vasi vasi > <[email protected]> > *Verzonden:* woensdag 22 mei 2024 13:38 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* [jallib] Linux executable > > Hi Rob, > > I see you provide executables for linux that are dynamically linked... > A statically linked executable can work on both glibc and musl based > distributions (Alpine and Void linux as two main examples as musl > platforms) no matter on which platform this was compiled (be it glibc or > musl), and it can also work on much older linux distros. It will help also > with old projects that require a specific version of jalv2 compiler. Right > now, a static link edit is possible only by modifying the Makefiles at > source level. > > I have a lot of old applications dynamically linked that do not work on > today's computers and operating systems. Is not only that many are written > in an old standard, not supported by the compiler, but in many cases, even > the GUI libraries are not available anymore. And jalv2 can be linked > statically. Maybe you don't know, but there are "recent" changes in GLIBC > that will prevent shared programs to work on linux distributions that have > GLIBC at a lower version than 2.34 (don't know if is the case of the jalv2 > compiler though). > > I think is in Jalv2 interest to avoid this vulnerability of Linux/UNIX > world. > > -- > Vasi > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/CABsDq%3D9%3D%3DPqrr7ffPaVDg3qSYTiwQKKhbroLpWucDDNjb9XrVA%40mail.gmail.com > <https://groups.google.com/d/msgid/jallib/CABsDq%3D9%3D%3DPqrr7ffPaVDg3qSYTiwQKKhbroLpWucDDNjb9XrVA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> > . > -- Vasi -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CABsDq%3D-nUyCPhH2a%2B3xgLg9U-O-WX3qXi5rhgY4pVemaF3AG6w%40mail.gmail.com.
