FS#14665 - XMoto doesn't build due to new GCC version

Attached to Project: Arch Linux
Opened by Sven-Hendrik Haase (Svenstaro) - Sunday, 10 May 2009, 14:40 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 14 May 2009, 12:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The XMoto 0.5.1-1 package currently in [extra] fails to build do to the more recent version of GCC (starting from GCC 4.3). While this is actually the project's fault, the package in [extra] should be patched until the XMoto project corrects this problem themselves. The Scorched3D package implements a GCC 4.3 patch that could be used as a guideline. The XMoto team has not yet addressed this problem in their SVN.

Additional info:
The errors produced when trying to compile with GCC 4.4:
XMArgs.cpp: In member function ‘void XMArguments::parse(int, char**)’:
XMArgs.cpp:121: error: ‘sscanf’ was not declared in this scope
XMArgs.cpp: In member function ‘void XMArguments::help(const std::string&)’:
XMArgs.cpp:572: error: ‘printf’ was not declared in this scope
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 14 May 2009, 12:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.0.1-2
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 10 May 2009, 15:35 GMT
add in the files that causes problem:

#include <stdio.h>

Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 10 May 2009, 15:37 GMT
Ooh is C++, ensure what headers use xmoto, this maybe is the correct:

#include <cstdio>
Comment by Ronald van Haren (pressh) - Sunday, 10 May 2009, 15:51 GMT
have you also filed a report upstream?
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 10 May 2009, 15:54 GMT
Upstream bug report already exists and includes a handy patch: http://todo.xmoto.tuxfamily.org/index.php?do=details&task_id=628
Comment by Ronald van Haren (pressh) - Thursday, 14 May 2009, 12:49 GMT
it is fixed in the xmoto 0.5.1-2 package. I had to remove my ~/.xmoto directory (probably not the whole directory was needed) to prevent the new version from crashing, so you may need to do so too.

Loading...