| Summary: | games-fps/doomlegacy-1.42 emerge fails with sys-devel/gcc-4.0.2 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Avuton Olrich <avuton> |
| Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | dogshu, farcaller, genzilla, hrabe, jkt, kanelxake, magnade, mal, patrizio.bassi, scott, spreetec, vanquirius |
| Priority: | High | Keywords: | PMASKED |
| Version: | 2005.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://sourceforge.net/tracker/index.php?func=detail&aid=1501896&group_id=2479&atid=102479 | ||
| Whiteboard: | Pending removal 13 Jan 2007 (mr_bones) | ||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 117482 | ||
|
Description
Avuton Olrich
2006-01-21 11:06:25 UTC
"GCC no longer accepts the -fwritable-strings option. Use named character arrays when you need a writable string." i added the following to the ebuild to get rid of that issue but the code itself needs some work im seeing about making a patch now sed -i \ -e "s:-fwritable-strings::" \ makefile \ || die "sed failed" i havent had any luck making a patch and upstream looks to be busy rewriting it all in c++... after deleting the obsolete switch...it compiles a bit stopping in : g_game.c:2324: error: invalid lvalue in increment g_game.c:2325: error: invalid lvalue in increment g_game.c:2326: error: invalid lvalue in increment g_game.c:2327: error: invalid lvalue in increment g_game.c:2335: error: invalid lvalue in increment g_game.c:2337: error: invalid lvalue in increment g_game.c:2341: error: invalid lvalue in increment g_game.c:2343: error: invalid lvalue in increment g_game.c:2346: error: invalid lvalue in increment g_game.c:2350: error: invalid lvalue in increment g_game.c:2352: error: invalid lvalue in increment g_game.c: In function ‘G_DoPlayDemo’: g_game.c:2523: error: invalid lvalue in increment make: *** [../objs/g_game.o] Error 1 *** Bug 146783 has been marked as a duplicate of this bug. *** *** Bug 146993 has been marked as a duplicate of this bug. *** *** Bug 147082 has been marked as a duplicate of this bug. *** should not be in portage marked as stable , as long it doesnt compile with the default GCC !!!! Sure, it should. We do not go around marking things back to testing. When this package was marked stable, it worked. Now that GCC 4.1 has been marked stable, it does not. That doesn't mean that this package is suddenly unstable. Anyway, the best course of action is a patch. Have one? The correct way is masking it since it no longer works by default and place a comment about why it masked if no patch/fix avaible? That's very likely. If we don't come up with a patch soon, this will likely be masked, then removed from the tree. (In reply to comment #11) > That's very likely. If we don't come up with a patch soon, this will likely be > masked, then removed from the tree. How much time normally passes before this kind of breakage is removed from the tree? It's package masked already. Removed from the tree. |
