Harry Putnam <rea...@newsguy.com> writes: > setup: > kernel-2.6.29-r2 > gcc-4.3.2-r3 > procmail is one tool that is absolutely robust and I expected no > trouble whatever emerging it... however the emerge is failing like > as shown below. I'm not sure what to do about getline. > > The only useflags that come up are one I set > `mbox' > and one other > `-selenix' > > [...] > ln ../src/procmail ../new/procmail > i486-pc-linux-gnu-gcc -c -O2 -march=i486 -pipe -fno-inline-functions > lockfile.c > i486-pc-linux-gnu-gcc -O2 -march=i486 -pipe -fno-inline-functions > lockfile.o exopen.o sublib.o acommon.o mcommon.o authenticate.o lastdirsep.o > -o lockfile -Wl,-z,now -Wl,-O1 -lm -lnsl -ldl -lc > ln ../src/lockfile ../new/lockfile > i486-pc-linux-gnu-gcc -c -O2 -march=i486 -pipe -fno-inline-functions > formail.c > In file included from formail.c:25: > formisc.h:20: error: conflicting types for 'getline' > /usr/include/stdio.h:651: error: previous declaration of 'getline' was here > make[1]: *** [formail.o] Error 1 > make[1]: Leaving directory > `/var/tmp/portage/mail-filter/procmail-3.22-r10/work/procmail-3.22/src' > make: *** [bins] Error 2 > * > * ERROR: mail-filter/procmail-3.22-r10 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 2527: Called die > * The specific snippet of code: > * emake CC="$(tc-getCC)" || die > * The die message: > * (no error message) > * > > * If you need support, post the topmost build error, and the call > stack if relevant. > > * A complete build log is located at > '/var/tmp/portage/mail-filter/procmail-3.22-r10/temp/build.log'. > > * The ebuild environment file is located at > *'/var/tmp/portage/mail-filter/procmail-3.22-r10/temp/environment'. > >
http://bugs.gentoo.org/show_bug.cgi?id=270551 HTH -- Education is the process of casting false pearls before real swine. -- Irwin Edman - This message may be digitally signed: GPG KeyID:0x9D2FD6C8 || FNMT SSL cert
