app-crypt/bsign-0.4.5 compiles and runs, please ~amd64 keyword it
Created attachment 79583 [details] emerge info
(In reply to comment #0) > app-crypt/bsign-0.4.5 compiles and runs, please ~amd64 keyword it Could you give a little bit more information about what you did to test this package? I tried compiling a simple C program "main(){}" and signing it, but it didn't appear to work for me... tcort@bobcat ~ $ bsign -s a.out bsign: file 'a.out' is not ELF tcort@bobcat ~ $ file a.out a.out: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.6, dynamically linked (uses shared libs), not stripped Doing the same on an x86 system seems to work... tcort@pan ~ $ bsign -s a.out Enter pass phrase: (blah blah blah) tcort@pan ~ $ file a.out a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.6, dynamically linked (uses shared libs), not stripped bobcat ~ # emerge --info Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.16-gentoo-r1 x86_64) ================================================================= System uname: 2.6.16-gentoo-r1 x86_64 AMD Turion(tm) 64 Mobile Technology ML-32 Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /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/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig cvs distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://adelie.polymtl.ca/ http://gentoo.arcticnetwork.ca/ http://gentoo.mirrored.ca/ http://gentoo.osuosl.org/ " MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /home/tcort/cvs/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac acpi aim alsa apache2 audacious audiofile avi berkdb bitmap-fonts browserplugin bzip2 cdr cli crypt ctype cups curl dba dbus dri eds emboss encode esd ethereal exif expat fam fastbuild flac foomaticdb force-cgi-redirect ftp gd gif glut gmp gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal icq idn imagemagick imlib ipv6 isdnlog jabber java jpeg kde lcms libwww lua lzw lzw-tiff mad memlimit mikmod mng mono motif mozilla moznocompose moznoirc moznomail mp3 mpeg msn ncurses nls nocd nptl nptlonly nsplugin offensive ogg oggvorbis openal opengl oscar pam pcre pdflib perl png posix pppd python qt quicktime readline sdl session shorten simplexml sndfile soap sockets speex spell spl ssl symlink tcpd tetex tiff tokenizer truetype truetype-fonts type1-fonts udev usb userlocales vorbis wxgtk1 xml xml2 xmms xpm xsl xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS
I made this bug request over TWO full months ago. I can not recall what specific actions were taken. As it was explained to me on #gentoo-amd64 at the time, to move a package from unkeyworded to ~arch it was simply required to compile and run without segfaulting. That philosophy which was expressed to me has either since fallen out of fashion, or was just plain wrong to begin with. Close this report, I could barely care less; I wouldn't ever even use this program -- I was simply trying to keep amd64 in sync with x86.
(In reply to comment #3) > As it was explained to me on #gentoo-amd64 at the time, to move a > package from unkeyworded to ~arch it was simply required to > compile and run without segfaulting. In addition to compiling and running, the program's major functionality must be tested. For example, a race car game should allow the user to drive around the track without the game crashing. More information on testing and ~amd64'ing here: http://www.gentoo.org/proj/en/base/amd64/tests/index.xml?part=1&chap=2 I did a little research and the upstream bug system (ie debian's bug system) has some bugs saying that it is for 32 bit binaries for now. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=148438 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=135666
