You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2013/03/20 21:01:15 UTC
[jira] [Assigned] (TS-1722) Compiling trunk on Fedora15/i686 fails
[ https://issues.apache.org/jira/browse/TS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach reassigned TS-1722:
-------------------------------
Assignee: Leif Hedstrom
Leif, you use Fedora ... can you verify whether master builds on Fedora 18?
> Compiling trunk on Fedora15/i686 fails
> --------------------------------------
>
> Key: TS-1722
> URL: https://issues.apache.org/jira/browse/TS-1722
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: C.R.
> Assignee: Leif Hedstrom
>
> Compiling newest trunk I receive the error message:
> make[2]: Entering directory `/home/tr/x/trafficserver/iocore/eventsystem'
> g++ -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib -I../../lib/records -I../../lib/ts -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_REENTRANT -Dlinux -march=i586 -g -pipe -Wall -Werror -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT UnixEventProcessor.o -MD -MP -MF .deps/UnixEventProcessor.Tpo -c -o UnixEventProcessor.o UnixEventProcessor.cc
> UnixEventProcessor.cc: In member function ‘virtual int EventProcessor::start(int)’:
> UnixEventProcessor.cc:186:194: error: format ‘%u’ expects argument of type ‘unsigned int’, but argument 8 has type ‘ink_thread {aka long unsigned int}’ [-Werror=format]
> UnixEventProcessor.cc:188:240: error: format ‘%u’ expects argument of type ‘unsigned int’, but argument 8 has type ‘ink_thread {aka long unsigned int}’ [-Werror=format]
> cc1plus: all warnings being treated as errors
> make[2]: *** [UnixEventProcessor.o] Error 1
> This happens on a Fedora release 15 system running 2.6.43.8-1.fc15.i686.PAE #1 SMP Mon Jun 4 20:21:39 UTC 2012 i686 i686 i386 GNU/Linux
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira