Opened 21 months ago

Last modified 9 months ago

#57686 assigned defect

libetpan @1.9.1: error: duplicate case value 'CURLE_PEER_FAILED_VERIFICATION'

Reported by: kencu (Ken) Owned by: pmetzger (Perry E. Metzger)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: libetpan

Description (last modified by kencu (Ken))

libetpan built fairly recently, but no longer builds for me. I presume some update to curl had caused it to fail now:

libtool: compile:  /opt/local/bin/clang-mp-3.9 -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src/data-types -I../../../src/low-level/imf -I/opt/local/include -DDEBUG -I/opt/local/include -D_REENTRANT -I/opt/local/include -I/opt/local/include -pipe -Os -arch x86_64 -W -Wall -c newsfeed_item.c -o newsfeed_item.o >/dev/null 2>&1
newsfeed.c:538:8: error: duplicate case value 'CURLE_PEER_FAILED_VERIFICATION'
  case CURLE_SSL_CACERT:
       ^
/opt/local/include/curl/curl.h:589:26: note: expanded from macro 'CURLE_SSL_CACERT'
#define CURLE_SSL_CACERT CURLE_PEER_FAILED_VERIFICATION
                         ^
newsfeed.c:533:8: note: previous case defined here
  case CURLE_SSL_PEER_CERTIFICATE:
       ^
/opt/local/include/curl/curl.h:610:36: note: expanded from macro 'CURLE_SSL_PEER_CERTIFICATE'
#define CURLE_SSL_PEER_CERTIFICATE CURLE_PEER_FAILED_VERIFICATION
                                   ^
1 error generated.
make[7]: *** [newsfeed.lo] Error 1

we still have the current version on the buildbots, it appears, presumably built against some previous curl.

Attachments (1)

main.log (327.5 KB) - added by kencu (Ken) 21 months ago.

Download all attachments as: .zip

Change History (4)

Changed 21 months ago by kencu (Ken)

Attachment: main.log added

comment:1 Changed 21 months ago by kencu (Ken)

Description: modified (diff)

comment:2 Changed 21 months ago by jmroot (Joshua Root)

Owner: set to pmetzger
Status: newassigned

Remember to assign to the maintainer.

comment:3 Changed 9 months ago by ryandesign (Ryan Schmidt)

libetpan 1.9.4 builds for me today. Do you still see this problem?

Note: See TracTickets for help on using tickets.