I'm also running into this issue. Will try out 1.3 for now. - Garret
On Oct 5, 7:19 am, Chuck Grindel <[email protected]> wrote: > I am having the same problem and would appreciate any suggestions. > > Thanks, > Chuck > > On Oct 5, 6:29 am, Jaume Sabater <[email protected]> wrote: > > > Hi everyone! > > > I have downloaded the recently released version 1.4 of beanstalkd and > > tried to compile it against libevent-1.4.2. When doing make, there is > > an error that appears (it's actually a warning, but due to the -Werror > > parameter it appears as error). > > > Here you are the details: > > > - Ubuntu 9.04 Server x86_64 (needed Python 2.6 and it was the fastest > > way) > > - Gcc 4.3.3 > > - Make 3.81 > > - Tried both with libevent-1.4.2 packages from Debian Sid and with > > compiled sources > > > Commands: > > > # pwd > > /usr/local/src/beanstalkd-1.4 > > # ./configure --prefix=/opt/beanstalkd-1.4 > > [..] > > # make > > make all-am > > make[1]: Entering directory `/usr/local/src/beanstalkd-1.4' > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > beanstalkd.o beanstalkd.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > binlog.o binlog.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > conn.o conn.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > job.o job.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > ms.o ms.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > net.o net.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > port.o port.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > pq.o pq.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > primes.o primes.c > > gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/include -c -o > > prot.o prot.c > > cc1: warnings being treated as errors > > prot.c: In function ‘fmt_stats’: > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 9 has type ‘uint64_t’ > > [..] > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 9 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 10 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 11 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 12 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 13 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 14 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 15 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 16 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 17 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 18 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 19 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 20 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 21 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 22 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 23 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 24 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 25 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 26 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 27 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 28 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 29 has type ‘uint64_t’ > > prot.c:852: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 30 has type ‘uint64_t’ > > prot.c: In function ‘fmt_job_stats’: > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 4 has type ‘uint64_t’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 8 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 9 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 10 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 11 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 4 has type ‘uint64_t’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 8 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 9 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 10 has type ‘usec’ > > prot.c:995: error: format ‘%llu’ expects type ‘long long unsigned > > int’, but argument 11 has type ‘usec’ > > make[1]: *** [prot.o] Error 1 > > make[1]: Leaving directory `/usr/local/src/beanstalkd-1.4' > > make: *** [all] Error 2 > > > I would like to know whether I can remove the -Werror parameter and > > assume the compilation will be/work fine, or whether this warning/ > > error should be fixed before the compilation can be "approved as > > valid". > > > Thanks in advance. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
