Summary: | dev-util/log4c-1.0.11.ebuild fails to build with gcc 3.4.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
Component: | [OLD] Unspecified | Assignee: | Daniel Black (RETIRED) <dragonheart> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ka0ttic |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | log4c_1.0.11_test.patch |
Description
f5d8fd51ed1e804c9e8d0357e8614e0493b06e96
2004-08-11 08:50:12 UTC
gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I../../src -DSRCDIR="\".\"" -O3 -march=i686 -funroll-loops -pipe -Wall -c `test -f 'bench.c' || echo './'`bench.c test_category.c: In function `test4': test_category.c:125: error: parse error before string constant test_category.c:127: error: parse error before string constant test_category.c:129: error: parse error before string constant make[3]: *** [test_category.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory `/var/tmp/portage/log4c-1.0.11/work/log4c-1.0.11/tests/log4c' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/log4c-1.0.11/work/log4c-1.0.11/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/log4c-1.0.11/work/log4c-1.0.11' make: *** [all] Error 2 !!! ERROR: dev-libs/log4c-1.0.11 failed. !!! Function src_compile, Line 41, Exitcode 2 !!! (no error message) Created attachment 37222 [details]
log4c_1.0.11_test.patch
ok, I have looked at the mess a bit... looks like gg 3.4.1 get confused by some
of the #define preprocessor-magic-stuff...
but I have found an easy way to get it to compile just fine anyway...
just changing the log-level of some of the tests from "trace" to "info" and it
will compile just fine (the trace level uses the bad magick)
Mine compiled fine with gcc-3.3 in the test part. It just failed when I ran the tests. I've applied your patch anyway. Thankyou. I'm going to email the author this patch along with the other on your behalf. ok? Thanks for the bug report. |