Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
libm 3.5.7/5.2.7
2011-04-15, 01:28 PM
Post: #1
libm 3.5.7/5.2.7
Announcing libm for Interix. Version ".7" (3.5.7 and 5.2.7).
This update added the "complex" API's and many "long" API's (the ones ending in "l").
This includes the static (libm.a) and shared (libm.so) libraries plus updates to the header files.

This update includes a definition for "complex" (using the gcc built-in) which should
not cause a functional problem and a reworking of "NaN" to work with the long API's.
With NaN you should have been using the "NAN" macros anyway.
If you use any NaN API's you will have to rebuild that objects.

This update is currently for Interix 3.5/5.2 and 6.0/6.1 all 32-bit systems.
The 64-bit system will get updated once the new gcc is finalized through testing
(yes, this is the 64-bit gcc to do shared libs on 64-bit machines).
Additional manual pages for the new API's too.

To update do:
    pkg_update -L libm


Find all posts by this user
Quote this message in a reply
2011-09-05, 11:20 PM
Post: #2
Re:libm 3.5.7/5.2.7
A note:
Found that when building an object with gcc the option "-std=gnu99" should
not be used because then the internal 'complex type' will not be used resulting in
error messages about the content of .
There are a number of configure scripts that will turn this option on. Worse you may
not see this option echoed to the screen because libtool may be run in silent mode.
(A check of the Makefile will show if "-std=gnu99" and/or "--silent" are used).
--FYI

Find all posts by this user
Quote this message in a reply
2011-09-28, 08:08 AM
Post: #3
Re:libm 3.5.7/5.2.7
Another note (about complex type):
If you are using g (or gnu c ) to built something in C that uses libm you may get the
same error message as described above for gcc, but you are not using the "-std=gnu99"
option (because it's not available, nor makes sense, with g ).
In all likelyhood you are using gcc/g 3.3 (check with a "which g " and look at the path).
The solution is to use the newer gcc/g 4.2 instead (adjust your path).
Then you should be okay.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)