365073 – sys-fs/cryptsetup disable static flag

Bug 365073 - sys-fs/cryptsetup disable static flag

Summary: sys-fs/cryptsetup disable static flag

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-04-27 11:04 UTC by Tolga Dalman
Modified:	2011-04-27 11:14 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tolga Dalman 2011-04-27 11:04:55 UTC

Can't emerge cryptsetup, because:

emerge: there are no ebuilds built with USE flags to satisfy "dev-libs/libgcrypt[static-libs]".
!!! One of the following packages is required to complete your request:
- dev-libs/libgcrypt-1.5.0_beta1-r1 (Change USE: +static-libs)
(dependency required by "sys-fs/cryptsetup-1.2.0-r1[static]" [ebuild])
(dependency required by "cryptsetup" [argument])

This bug is similar to bug 351810.

USE=-static emerge cryptsetup works perfectly. 


Reproducible: Always

Comment 1 Samuli Suominen (RETIRED) gentoo-dev

2011-04-27 11:08:11 UTC

Read the output again, it's asking for you to enable USE=static-libs for libgcrypt.

Standard portage output for USE dependencies.

Comment 2 Tolga Dalman 2011-04-27 11:14:11 UTC

I have neither static nor static-libs modified. Why do I have to set static or static-libs in the first place ?
Thus, I suggest either to remove static from cryptsetup OR add static-libs to
libgcrypt. What am I missing ?