The newest version of omniORBpy in portage (4.0.5 as of this message) does not actually build SSL support even if the SSL USE flag is turned on. The configure should have the --with-openSSL flag turned on when the USE flag is set. The underlying omniORB C++ libraries seem to work fine with the SSL flag. Reproducible: Always Steps to Reproduce: 1. emerge omniORB.py 2. Note the configure parameters in the ebuild... even if the USE flage is set for ssl the --with-openSSL flag is not set. 3. Actual Results: omniORBpy compiles and installs, but without SSL support Expected Results: It should have compiled with SSL support and installed Portage 2.0.51-r15 (default-linux/x86/2004.0, gcc-3.4.3, glibc-2.3.3.20040420-r2,glibc-2.3.4.20041102-r0, 2.6.9-mm1 i686) ================================================================= System uname: 2.6.9-mm1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.3-r1,dev-lang/python-2.3.4-r1,dev-lang/python-2.4-r2 [2.4 (#1, Feb 12 2005, 20:07:22)] dev-lang/python: 2.3.3-r1, 2.3.4-r1, 2.4-r2 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.7.9-r1, 1.8.5-r3, 1.6.3, 1.9.4, 1.5 sys-devel/binutils: 2.14.90.0.8-r1, 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2, 2.6.8.1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -mmmx -msse -msse2 -mfpmath=sse -O2 -fomit-frame-pointer -fforce-addr -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -mmmx -msse -msse2 -mfpmath=sse -O2 -fomit-frame-pointer -fforce-addr -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ http://gentoo.mirrors.pair.com/ http://adelie.polymtl.ca/ ftp://mirrors.tds.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apm arts avi berkdb bitmap-fonts cdr chroot crypt cups curl dvd encode esd f77 fam flac font-server foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imagemagick imlib ipv6 java jpeg junit kde ldap libg++ libwww mad mikmod mmx motif mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pdflib perl plotutils png python qt quicktime readline samba sdl slang spell sse sse2 ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Update to original comments: The omniORBpy version is actually 2.5 which is built on top of the base omniORB which is version 4.0.5
This has nothing to do with developer relations, particularly not the developers howto, which was apparently chosen at random. If you don't know where a bug should go, please don't assign it.
fixed in portage, due to stupid typo!
