Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1426 closed Bug (fixed)

can't statically link cli, daemon, or gtk client: curl & openssl link order is reversed

Reported by: lubomir.marinov Owned by: charles
Priority: Normal Milestone: 1.40
Component: Transmission Version: 1.34
Severity: Normal Keywords:
Cc:

Description

In r7061 and on Windows+MinGW at least when linking transmissioncli statically to libcurl and openssl, the operation fails with unresolved external OPENSSL symbols. I think it's because cli/Makefile.am (therefore, cli/Makefile) has the libs specified to the linker in transmissioncli_LDADD in the order $(OPENSSL_LIBS) $(LIBCURL_LIBS). But because libcurl depends on openssl, the order should be $(LIBCURL_LIBS) $(OPENSSL_LIBS).

Change History (3)

comment:1 Changed 12 years ago by charles

  • Component changed from CLI to Transmission
  • Milestone changed from None Set to 1.40
  • Status changed from new to assigned
  • Version set to 1.34

comment:2 Changed 12 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

fixed in r7062

comment:3 Changed 12 years ago by charles

  • Summary changed from Win32/MinGW CLI static linking to curl and openssl needs $(LIBCURL_LIBS) $(OPENSSL_LIBS) order to can't statically link cli, daemon, or gtk client: curl & openssl link order is reversed
Note: See TracTickets for help on using tickets.