i686-pc-linux-gnu-gcc -DDEFAULT_CHARSET_HOME=\"/usr\" -DDATADIR=\"/var/lib/mysql\" -DSHAREDIR=\"/usr/share/mysql\" -DDONT_USE_RAID -I. -I. -I.. -I./../include -I../include -I./.. -I.. -I.. -O3 -DDBUG_OFF -march=i686 -funroll-loops -pipe -O3 -c libmysql.c -Wp,-MD,.deps/libmysql.TPlo -fPIC -DPIC -o .libs/libmysql.lo In file included from /usr/include/linux/config.h:4, from /usr/include/asm/atomic.h:4, from ../include/global.h:224, from libmysql.c:18: /usr/include/linux/autoconf.h:64: warning: `CONFIG_SMP' redefined ../include/global.h:223: warning: this is the location of the previous definition libmysql.c: In function `mysql_real_connect': libmysql.c:1340: warning: passing arg 5 of `gethostbyname_r' from incompatible pointer type libmysql.c:1340: too few arguments to function `gethostbyname_r' libmysql.c:1340: warning: assignment makes pointer from integer without a cast make[2]: *** [libmysql.lo] Error 1 make[2]: Leaving directory `/var/tmp/portage/mysql-3.23.54a/work/mysql-3.23.54a/libmysql_r' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/mysql-3.23.54a/work/mysql-3.23.54a' make: *** [all] Error 2 !!! ERROR: dev-db/mysql-3.23.54a failed. !!! Function src_compile, Line 99, Exitcode 2 !!! compile problem
smp huh? i dont have any SMP blizzy. would be nice if you came up with a fix.
Nope, I don't have SMP either.
libmysql.c:1340: too few arguments to function `gethostbyname_r' well blizzy, more info please. gcc, glibc, blah, blah. i dont have any clues jumping out at me off-the-bat, but we'll keep trying ;-)
glibc-2.2.5-r7, gcc-2.95.3-r7 Don't hesitate to ask if you need more info.
maybe your sed is too new? i think theres was a buggy version causing mysterious compile failures. sorry blizzy, out of ideas.
blizzy, nobody else has reported problems with this either.
Yes, I see. Actually I'm not sure the problem still exists because I didn't find the time to retry it yet. I will do that later this day.
I'm sorry for the delay. Somehow, with all the updating of other packages over time, this bug seems to be gone. I'm herewith closing this bug.