After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703397 - ./configure --with-long-double fails on last version of GCC
./configure --with-long-double fails on last version of GCC
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Compilation
1.12.x
Other Linux
: Normal minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-07-01 14:46 UTC by david
Modified: 2013-07-01 23:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Config.log after running export CC="gcc -lm" ; ./configure --with-long-double ; (203.82 KB, text/x-log)
2013-07-01 14:46 UTC, david
Details
config.log in case of failure (167.70 KB, text/x-log)
2013-07-01 16:52 UTC, david
Details

Description david 2013-07-01 14:46:55 UTC
Created attachment 248153 [details]
Config.log after running export CC="gcc -lm" ; ./configure --with-long-double ;

I am using archlinux, a rolling-release distribution, and so the last versions of GCC and autotools is meant to be used when compiling.

I just downloaded the tarball from this link : http://ftp.gnome.org/pub/GNOME/sources/gnumeric/1.12/gnumeric-1.12.3.tar.xz

I extracted it and ran the configure script by doing :


cd ~/src/
wget http://ftp.gnome.org/pub/GNOME/sources/gnumeric/1.12/gnumeric-1.12.3.tar.xz
xz -d gnumeric-1.12.3.tar.xz ; 
tar xvf gnumeric-1.12.3.tar ; 
cd gnumeric-1.12.3 ; 
./configure --with-long-double ;

The script ends up failing with the two following lines :

checking for lgamma_r... no
checking for lgamma_r in -lm... yes
checking for lgamma... yes
checking sunmath.h usability... no
checking sunmath.h presence... no
checking for sunmath.h... no
checking for go_render_generall... yes
checking for fabsl... no
configure: error: Long doubles require the  function.

This is solved if one does before running the configure script by doing :

export CC="gcc -lm" ; ./configure --with-long-double ;
Comment 1 Morten Welinder 2013-07-01 15:01:56 UTC
Can you please attach config.log from the failing configure too?
Comment 2 david 2013-07-01 16:52:25 UTC
Created attachment 248166 [details]
config.log in case of failure
Comment 3 Morten Welinder 2013-07-01 23:17:32 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.