Attached two files. First is the actual ebuild for licq 1.2.0a. Second is a patch for the configure files. Seems there's a warning using vector.h, so I had to add -Wno-deprecated for the test to succeed. The patch needs to be put in the files subdirectory for the ebuild to pick it up. The gtk and console plugins do not compile on gcc 3.1, but the qt and kde seem to work perfectly....
Created attachment 2712 [details] Ebuild File
Created attachment 2713 [details, diff] Configure patch
This should be marked as a duplicate of bug 5661.
Note that the ebuild for 1.2.0a is now in the portage tree (bug 5661). I don't know whether we need to include the configure patch from this bug report, but it looks like it might just fix the problem that Bart Verwilst was talking about in his comment to bug 5661. Bart, could you see whether the patch works for you (I'm still using gcc 2.95 here and not planning to switch ;^) )?
The configure patch does fix that problem with vector.h... Just tried to compile the portage ebuild and got this error: checking for vector.h... no configure: error: You need to have the libstdc++ headers installed Applying the patch will fix this....
I agree with Matt, I got the same error with the current ebuild in portage (the vector.h ). So I put the patch in the files dir and edited the current ebuild to apply the patch, et voila, licq emerges.
I've tested the patch, so I'll take this bug, if that's okay. ;^)
I've added the patch to the CVS (licq-1.2.0a-r1). Matt, Sven, could you please test the new ebuild? Thanks.
Relaized that Sven was not on the CC list. Sven, could you please test the -r1? Thanks.
Works great for me!
