Bug 442694 – x11-libs/libqxt-0.6.2 - failed to configure with USE="-ssl"

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sergey Popov 2012-11-11 10:40:59 UTC]

Created attachment 329190 [details]
build.log

phantom / # emerge -1 x11-libs/libqxt -pv

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] x11-libs/libqxt-0.6.2  USE="-berkdb -debug -doc -sql -ssl -web -xscreensaver -zeroconf" 0 kB

Total: 1 package (1 new), Size of downloads: 0 kB

Package failed with: 'Unrecognized configure option: -no-openssl'
With USE="ssl" build succeeded.

build.log attached.

my emerge --info:
Portage 2.1.11.9 (default/linux/amd64/10.0/developer, gcc-4.6.3, glibc-2.14.1-r3, 3.4.9-gentoo-BADO x86_64)
=================================================================
System uname: Linux-3.4.9-gentoo-BADO-x86_64-Intel-R-_Core-TM-_i7_CPU_950_@_3.07GHz-with-gentoo-2.1
Timestamp of tree: Sat, 10 Nov 2012 23:15:01 +0000
app-shells/bash:          4.2_p20
dev-lang/python:          2.7.3-r2, 3.2.3
dev-util/cmake:           2.8.9
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.68
sys-devel/automake:       1.11.6
sys-devel/binutils:       2.21.1-r1
sys-devel/gcc:            4.5.3-r2, 4.6.3
sys-devel/gcc-config:     1.6
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 3.1 (virtual/os-headers)
sys-libs/glibc:           2.14.1-r3
Repositories: gentoo pinkbyte
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/openvpn/easy-rsa"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe"
DISTDIR="/bound/distfiles"
EMERGE_DEFAULT_OPTS=""
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs collision-protect config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuild-head protect-owned sandbox sfperms sign splitdebug strict test test-fail-continue unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles"
LANG="ru_RU.UTF-8"
LDFLAGS="-Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed"
LINGUAS="ru ru_RU"
MAKEOPTS="-j9"
PKGDIR="/bound/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/bound/portage"
PORTDIR_OVERLAY="/bound/overlays/pinkbyte"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 multilib" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LINGUAS="ru ru_RU" PYTHON_TARGETS="python2_7" USERLAND="GNU" VIDEO_CARDS="nvidia"
Unset:  CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

[Comment 1 Michael Palimaka (kensington) 2012-11-12 11:09:00 UTC]

Not sure how that ever got stabilised...but in any case, thanks, fixed in CVS.

+  12 Nov 2012; Michael Palimaka <[e-mail]> libqxt-0.6.2.ebuild:
+  Remove invalid USE flag wrt bug #442694.

[Comment 2 Davide Pesavento (RETIRED) 2012-11-12 22:10:16 UTC]

(In reply to comment #1)
> Not sure how that ever got stabilised...but in any case, thanks, fixed in
> CVS.
> 
> +  12 Nov 2012; Michael Palimaka <[e-mail]> libqxt-0.6.2.ebuild:
> +  Remove invalid USE flag wrt bug #442694.

Thanks a lot Michael! Can you also sync the live ebuild in qt overlay please?

[Comment 3 Michael Palimaka (kensington) 2012-11-13 15:49:12 UTC]

(In reply to comment #2)
> Thanks a lot Michael! Can you also sync the live ebuild in qt overlay please?

Interestingly, the live ebuild works fine but the code handling -no-openssl is a few years old. I wonder if the tarball is a bit funny?

[Comment 4 Davide Pesavento (RETIRED) 2012-11-13 21:31:21 UTC]

Interesting indeed. Well, let's keep the flag in 9999 then.