Flint for Linux Support FAQ

 

Q:   I installed Flint on CentOS 8.  I get the following message and my Fortran-lint license daemon (iptlmd) stops!

***glibc detected *** iptlmd: double free or corruption (!prev)  

A:   Later versions of glibc take a proactive step in preventing heap corruption. However, the message is quite common, does
not necessarily mean the program is going to crash, and the problem may not even be in the application code.  It has even
been reported to occur when glibc versions differ between the compile and user workstations!

This message is being reported for our 3rd party license manager. It’s important to note we have no record of receiving, in
two decades, any support issues surrounding crashes in the license daemon.

For this reason, we suggest the following workaround, which instructs glibc to bypass this check on the code:

export MALLOC_CHECK_=0

So we can keep track of the frequency in our customer base, please advise [email protected] if you experienced this
issue and whether the workaround has had the desired effect.

 

Q:   My Flint GUI fonts look terrible!

A:   Please see this faq.

 

Q:   I installed Flint on RHEL 6.  When I try to run the GUI, I get error messages like one of these and the GUI does not start.

Error: Please install the module ‘Tk’
Can't load '/…/Tk/Tk.so' for module Tk: libX11.so.6

A:   UPDATED 21-Sep-18  There is a new version of Flint/Linux that is 100% 64-bit!
You can get it from the same Downloads page; just choose the 64-bit link. For the foreseeable future, Cleanscape will
maintain separate 32-bit and 64-bit versions.

A couple notes:
1. This version requires glibc_2.14 or later. Since this dates back to 2011, we feel this is a safe compromise.
2. The xlint source level browser is fully deprecated and will not be available with this release.
3. If either of these conditions are an issue for you, let us know, proceed with the 32-bit version, and continue reading.


A:   The message is a catch-all and has been updated in version 7.1 of the GUI to be more descriptive.  Meanwhile, here is the
cause and solution:


If you have a 64-bit Linux like RHEL or CentOS AND the default 64-bit-only installation was used, the i686 libraries are missing.
CentOS5 and RHEL5 installed i686 libraries but it appears version 6 installs only x86_64 libraries by default.

To correct this issue, install the following files (example installation code is shown to the right) -
libX11.so.6     
yum install libX11.i686
ld-linux.so      
yum install glibc.i686

 

The below question is deprecated.

Q:   Whenever I start Flint on Red Hat, I get this weird message, but everything seems to run:

Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed.

A:   The message is annoying but harmless.  This can be eliminated by setting global variable LD_ASSUME_KERNEL to 2.4.1 – either

setenv LD_ASSUME_KERNEL 2.4.1 or

export LD_ASSUME_KERNEL=2.4.1 or

LD_ASSUME_KERNEL=2.4.1;export LD_ASSUME_KERNEL

depending on shell used.

 

You can check out other FAQs related to Cleanscape Flint by clicking here.

      

CLEANSCAPE SUPPORT CONTACT INFO

[email protected]

800-944-5468 (aka 800-94-4LINT)