This doesn't look like it's an error on my system, so I'm opening a bug on it... --22:21:40-- http://www.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/ElectricFence-2.2.2.tar.gz => `/usr/portage/distfiles/ElectricFence-2.2.2.tar.gz' Connecting to proxy[172.16.1.16]:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 28,247 [application/x-tar] 100%[======================================================>] 28,247 151.57K/s ETA 00:00 22:21:40 (151.57 KB/s) - `/usr/portage/distfiles/ElectricFence-2.2.2.tar.gz' saved [28247/28247] >>> md5 ;-) ElectricFence-2.2.2.tar.gz >>> Unpacking source... >>> Unpacking ElectricFence-2.2.2.tar.gz >>> Source unpacked. cc -g -DUSE_SEMAPHORE -fPIC -c efence.c -o efence.o cc -g -DUSE_SEMAPHORE -fPIC -c page.c -o page.o cc -g -DUSE_SEMAPHORE -fPIC -c print.c -o print.o cc -g -DUSE_SEMAPHORE -fPIC -c tstheap.c -o tstheap.o print.c: In function `EF_Printv': print.c:114: `char' is promoted to `int' when passed through `...' print.c:114: (so you should pass `int' not `char' to `va_arg') make: *** [print.o] Error 1 make: *** Waiting for unfinished jobs....
gcc version, glibc version and CFLAGS/CXXFLAGS please?
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.4/specs Configured with: /usr/local/portage_tmp//portage/gcc-3.0.4-r6/work/gcc-3.0.4/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share/gcc-3.0.4 --enable-shared --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i686-pc-linux-gnu --enable-threads=posix --disable-checking --with-local-prefix=/usr/local --with-system-zlib --enable-shared --enable-nls --without-included-gettext --program-suffix=-3.0 : (reconfigured) Thread model: posix gcc version 3.0.4 CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" How would I get the glibc version?
This seems to work with gcc-3.2. Any chance you can try this with a more recent compiler ?
This appears to be a problem with gcc 3.0.4; it works with 2.95.3 and 3.2. We don't support gcc-3.0.x nor gcc-3.1.x, so I'm closing this bug.