| Summary: | dev-vcs/git-2.6.3-r1 USE=curl fails to build with dev-libs/libressl-2.5.0 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Felix Janda <felix.janda> |
| Component: | Current packages | Assignee: | Anthony Basile <blueness> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | polynomial-c, robbat2, tsmksubc |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 561854 | ||
| Attachments: | build log | ||
I can confirm that git-2.14.2 USE=curl compiles just fine with libressl-2.6.2 and curl-7.55.1. All of these versions are in portage, so I believe the bug can be closed now. I cannot reproduce this any more. This was probably caused by a miscompiled libcurl. Closing as Invalid. |
Created attachment 448690 [details] build log It seems that with curl linked against dev-libs/libressl-2.5.0 it is necessary to pass "-lssl" when linking against libcurl. For dev-vcs/git this leads to linking failures as illustrated in the attached build log. upstream git properly detects whether "-lssl" is needed, but the ebuild does not use the upstream configure script. (Why??) With NEEDS_SSL_WITH_CURL added to the make opts, the package compiles fine.