Summary: | licq-1.2.7 falis to compile with gcc 3.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Peter <b0fh> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mohk, pkdawson, voxus |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 48528 | ||
Attachments: |
licq-1.2.7.ebuild-gcc34.patch
1.2.7-gcc34.patch |
Description
Robert Peter
2004-05-23 03:27:25 UTC
Created attachment 34546 [details, diff]
licq-1.2.7.ebuild-gcc34.patch
ebuild patch to add -fpermissive to CXXFLAGS and apply a patch (see next
attachment)
Created attachment 34547 [details, diff]
1.2.7-gcc34.patch
Not yet tested with qt or kde USE flags.
Tested with qt and kde flags, no further problems encountered. works here perfectly, please update ebuild... licq is masked on amd64 or i would test this. that and fixes that force the use of -fpermissive dont make me too confident... Hi Travis, As I understand it, using -fpermissive is kind of like turning off -Werror. GCC knows exactly how to compile the code, but it doesn't want to because it's not "standard" C++. The code should still be fixed of course, but I figured I'd leave it up to the authors of licq to decide how to do that :) licq-1.3.0_pre is in portage may this one should be closed? Yeah, works for me (gcc-3.4.1-r2 and licq-1.3.0_pre-r4). The crypt flag is broken, but that's not gcc34-specific. Open a new bug or reopen this one in case you find new gcc-3.4 issues with the latest version of licq, but it looks like this one has been fixed upstream. |