Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17366 - [cmake] generate wrong cross-compiler flags

Attached to Project: Arch Linux
Opened by YP (knedlyk) - Thursday, 03 December 2009, 14:43 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 10 December 2009, 12:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading to the 2.8.0 version cmake starts to generate wrong C and c++ flags (see Steps to reproduce).

Steps to reproduce:
Build guayadeque from AUR:
yaourt -S guayadeque

c++: _FILE_OFFSET_BITS=64: No such file or directory
c++: _LARGE_FILES: No such file or directory
c++: __WXGTK__: No such file or directory

I found, that the problem was in ... guayadeque/src/guayadeque-0.2.0/src/CMakeFiles/guayadeque.dir/flags.make, where C_FLAGS at the end of string and C_DEFINES have the same entry: -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ . The same is with CXX_FLAGS and CXX_DEFINES. I simply deleted "-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__" from the ends of C_FLAGS and CXX_FLAGS strings and after that compilation went smoothly.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Thursday, 10 December 2009, 12:38 GMT
Reason for closing:  Upstream
Additional comments about closing:  http://sourceforge.net/tracker/?func=det ail&aid=2908426&group_id=250783& amp;atid=1126447
Comment by YP (knedlyk) - Thursday, 03 December 2009, 15:08 GMT
Downgrading to cmake-2.6.4 solves this issue. But it's not a solution.
Comment by Pierre Schmitz (Pierre) - Thursday, 03 December 2009, 21:10 GMT
It would be best to report this to the guayadeque project as this is very unlikely a packaging issue.
Comment by YP (knedlyk) - Thursday, 03 December 2009, 21:43 GMT
I'll do that, but why the previous version of cmake worked fine?
Comment by YP (knedlyk) - Wednesday, 09 December 2009, 18:09 GMT
Well, I reported this issue to a guayadeque maintainer, and finally he fixed this in svn version.

Loading...