games-fps/enemy-territory-2.56-r2 dosn't work, then trying to run it, a error is given: /usr/games/bin/et: line 3: aoss32: command not found Reproducible: Always Steps to Reproduce: 1.install games-fps/enemy-territory-2.56-r2 2.$ et /usr/games/bin/et: line 3: aoss32: command not found Actual Results: game dosn't run Expected Results: game running # Copyright 2000-2003 Daniel Robbins, Gentoo Technologies, Inc. # Contains local system settings for Portage system # $Header: /home/cvsroot/gentoo-src/portage/cnf/make.conf,v 1.70 2004/01/12 07:34:38 carpaski Exp $ # Please review 'man make.conf' for more information. # Build-time functionality # ======================== # # The USE variable is used to enable optional build-time functionality. For # example, quite a few packages have optional X, gtk or GNOME functionality # that can only be enabled or disabled at compile-time. Gentoo Linux has a # very extensive set of USE variables described in our USE variable HOWTO at # http://www.gentoo.org/doc/use-howto.html # # The available list of use flags with descriptions is in your portage tree. # Use 'less' to view them: --> less /usr/portage/profiles/use.desc <-- # # 'ufed' is an ncurses/dialog interface available in portage to make handling # useflags for you. 'emerge app-admin/ufed' # # Example: USE="3dnow 3dnowex acpi4linux avi bash-completion bigger-fonts bzlib \ cdparanoia cdrom chroot codecs curl curlwrappers dga divx4linux dvb \ dvd dvdr dvdread editor emacs encode escreen etwin evo exif \ extensions faac fame fbcon fbdev ffmpeg flash freetype fs ftp gimp \ gkrellm gnome graphviz gs gtk2 hardened hardenedphp icon iconv icq \ image imagekits imagemagick imap innodb irda jabber java jbig jikes \ latex lcms lirc live lm_sensors maildir md5sum mime mimencode mixer \ mjpeg mmx mng mp3 mpeg mpeg4 mplayer msn music mythtv native net \ nvidia openssh pda pdf pdfkit pdflib portaudio posix pthreads \ quicktime real sasl spell sse sse2 theora threads tidy transcode v4l \ v4l2 videos vim wmf X xalan xine xinerama xsl xvid -fortran -cups" # Host Setting # ============ # # If you are using a Pentium Pro or greater processor, leave this line as-is; # otherwise, change to i586, i486 or i386 as appropriate. All modern systems # (even Athlons) should use "i686-pc-linux-gnu". All K6's are i586. # #CHOST="i686-pc-linux-gnu" CHOST="x86_64-pc-linux-gnu" # Host and optimization settings # ============================== # # For optimal performance, enable a CFLAGS setting appropriate for your CPU. # # Please note that if you experience strange issues with a package, it may be # due to gcc's optimizations interacting in a strange way. Please test the # package (and in some cases the libraries it uses) at default optimizations # before reporting errors to developers. # # -mcpu=<cpu-type> means optimize code for the particular type of CPU without # breaking compatibility with other CPUs. # # -march=<cpu-type> means to take full advantage of the ABI and instructions # for the particular CPU; this will break compatibility with older CPUs (for # example, -march=athlon-xp code will not run on a regular Athlon, and # -march=i686 code will not run on a Pentium Classic. # # CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp, # athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686 # (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), # pentium3, and pentium4. # # Note that Gentoo Linux 1.4 and higher include at least gcc-3.2. # # CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686 # (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95* # # CRITICAL WARNINGS: ****************************************************** # # K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. # # ************************************************************************* # # # Decent examples: # #CFLAGS="-mcpu=athlon-xp -O3 -pipe" CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" # If you set a CFLAGS above, then this line will set your default C++ flags to # the same settings. CXXFLAGS="${CFLAGS}" # Advanced Masking # ================ # # Gentoo is using a new masking system to allow for easier stability testing # on packages. KEYWORDS are used in ebuilds to mask and unmask packages based # on the platform they are set for. A special form has been added that # indicates packages and revisions that are expected to work, but have not yet # been approved for the stable set. '~arch' is a superset of 'arch' which # includes the unstable, in testing, packages. Users of the 'x86' architecture # would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages. # '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms. # # Please note that this is not for development, alpha, beta, nor cvs release # packages. "Broken" packages will not be added to testing and should not be # requested to be added. Alternative routes are available to developers # for experimental packages, and it is at their discretion to use them. # # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST. # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS. # ACCEPT_KEYWORDS="amd64" # Portage Directories # =================== # # Each of these settings controls an aspect of portage's storage and file # system usage. If you change any of these, be sure it is available when # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" *** # # PORTAGE_TMPDIR is the location portage will use for compilations and # temporary storage of data. This can get VERY large depending upon # the application being installed. #PORTAGE_TMPDIR=/var/tmp # # PORTDIR is the location of the portage tree. This is the repository # for all profile information as well as all ebuilds. This directory # itself can reach 200M. WE DO NOT RECOMMEND that you change this. #PORTDIR=/usr/portage # # DISTDIR is where all of the source code tarballs will be placed for # emerges. The source code is maintained here unless you delete # it. The entire repository of tarballs for gentoo is 9G. This is # considerably more than any user will ever download. 2-3G is # a large DISTDIR. #DISTDIR=${PORTDIR}/distfiles # # PKGDIR is the location of binary packages that you can have created # with '--buildpkg' or '-b' while emerging a package. This can get # upto several hundred megs, or even a few gigs. #PKGDIR=${PORTDIR}/packages # # PORT_LOGDIR is the location where portage will store all the logs it # creates from each individual merge. They are stored as YYMMDD-$PF.log # in the directory specified. This is disabled until you enable it by # providing a directory. Permissions will be modified as needed IF the # directory exists, otherwise logging will be disabled. #PORT_LOGDIR=/var/log/portage # # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without # concern that they will be deleted by rsync updates. Default is not # defined. PORTDIR_OVERLAY=/usr/local/portage # Fetching files # ============== # # If you need to set a proxy for wget or lukemftp, add the appropriate "export # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if # all users on your system should use them. # # Portage uses wget by default. Here are some settings for some alternate # downloaders -- note that you need to merge these programs first before they # will be available. # # Default fetch command (5 tries, passive ftp for firewall compatibility) #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}" #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}" # # Using wget, ratelimiting downloads #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}" #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}" # # Lukemftp (BSD ftp): #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}" #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}" # # Prozilla (turbo downloader) #FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}' # # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval. # The list is a space seperated list which is read left to right. If you use # another mirror we highly recommend leaving the default mirror at the end of # the list so that portage will fall back to it if the files cannot be found # on your specified mirror. We _HIGHLY_ recommend that you change this setting # to a nearby mirror by merging and using the 'mirrorselect' tool. GENTOO_MIRRORS="ftp://ftp.gentoo.diku.dk http://ftp.easynet.nl/mirror/gentoo/ http://gentoo.mirror.sdv.fr http://www.gigaload.org/gentoo.org/ http://gentoo.math.bme.hu http://gentoo.mirror.icd.hu/" # # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages. # The list is a single extry specifying the full address of the directory # serving the tbz2's for your system. Running emerge with either '--getbinpkg' # or '--getbinpkgonly' will cause portage to retrieve the metadata from all # packages in the directory specified, and use that data to determine what will # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please # consult the man pages and 'emerge --help' for more information. #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/" #PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/" # Synchronizing Portage # ===================== # # Each of these settings effects how Gentoo synchronizes your Portage tree. # Synchronization is handled by rsync and these settings allow some control # over how it is done. # # # SYNC is the server used by rsync to retrieve a localized rsync mirror # rotation. This allows you to select servers that are geographically # close to you, yet still distribute the load over a number of servers. # Please do not single out specific rsync mirrors. Doing so places undue # stress on particular mirrors. Instead you may use one of the following # continent specific rotations: # # Default: "rsync://rsync.gentoo.org/gentoo-portage" # North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage" # South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage" # Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage" # Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage" # Australia: "rsync://rsync.au.gentoo.org/gentoo-portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" # # RSYNC_RETRIES sets the number of times portage will attempt to retrieve # a current portage tree before it exits with an error. This allows # for a more successful retrieval without user intervention most times. #RSYNC_RETRIES="3" # # RSYNC_TIMEOUT sets the length of time rsync will wait before it times out # on a connection. Most users will benefit from this setting as it will # reduce the amount of 'dead air' they experience when they run across # the occasional, unreachable mirror. Dialup users might want to set this # value up around the 300 second mark. RSYNC_TIMEOUT=60 # Advanced Features # ================= # # MAKEOPTS provides extra options that may be passed to 'make' when a # program is compiled. Presently the only use is for specifying # the number of parallel makes (-j) to perform. The suggested number # for parallel makes is CPUs+1. #MAKEOPTS="-j2" # # PORTAGE_NICENESS provides a default increment to emerge's niceness level. # Note: This is an increment. Running emerge in a niced environment will # reduce it further. Default is unset. #PORTAGE_NICENESS=3 # # AUTOCLEAN enables portage to automatically clean out older or overlapping # packages from the system after every successful merge. This is the # same as running 'emerge -c' after every merge. Set with: "yes" or "no". # This does not affect the unpacked source. See 'noclean' below. #AUTOCLEAN="yes" # # FEATURES are settings that affect the functionality of portage. Most of # these settings are for developer use, but some are available to non- # developers as well. # # 'autoaddcvs' causes portage to automatically try to add files to cvs # that will have to be added later. Done at generation times # and only has an effect when 'cvs' is also set. # 'buildpkg' causes binary packages to be created of all packages that # are merged. # 'ccache' enables ccache support via CC. # 'cvs' feature for developers that causes portage to enable all # cvs features (commits, adds) and all USE flags in SRC_URI # will be applied for digests. # 'digest' autogenerate a digest for packages. # 'distcc' enables distcc support via CC. # 'fixpackages' allows portage to fix binary packages that are stored in # PKGDIR. This can consume a lot of time. 'fixpackages' is # also a script that can be run at any given time to force # the same actions. # 'keeptemp' prevents the clean phase from deleting the temp files ($T) # from a merge. # 'keepwork' prevents the clean phase from deleting the WORKDIR. # 'noauto' causes ebuild to perform only the action requested and # not any other required actions like clean or # 'noclean' prevents portage from removing the source and temporary files # after a merge -- for debugging purposes only. # 'nostrip' prevents stripping of binaries. # 'notitles' disables xterm titlebar updates (which contain status info). # 'sandbox' enable sandbox-ing when running emerge and ebuild # 'strict' causes portage to react strongly to conditions that # have the potential to be dangerous -- like missing or # incorrect Manifest files. # 'userpriv' allows portage to drop root privleges while it is compiling # as a security measure, and as a side effect this can remove # sandbox access violations for users. # 'usersandbox' enables sandboxing while portage is running under userpriv. # unpack -- for debugging purposes only. FEATURES="sandbox ccache userpriv usersandbox" # # CCACHE_SIZE sets the space use limitations for ccache. The default size is # 2G, and will be set if not defined otherwise and ccache is in features. # Portage will set the default ccache dir if it is not present in the # user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache # (/var/tmp/ccache), and for regular use the default is /root/.ccache. # Sizes are specified with 'G' 'M' or 'K'. # '4G' for 4 gigabytes, '4096M' for 4 gigabytes, etc... Default is 2G CCACHE_SIZE="8G" # # DISTCC_DIR sets the temporary space used by distcc. #DISTCC_DIR="${PORT_TMPDIR}/.distcc" # # RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates # the portage tree. Specific chucks of the tree may be excluded from # consideration. This may cause dependency failures if you are not careful. # The file format is one pattern per line, blanks and ';' or '#' lines are # comments. See 'man rsync' for more details on the exclude-from format. #RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes gcc -v Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/specs Configured with: /var/tmp/portage/gcc-3.4.3/work/gcc-3.4.3/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3 --host=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --enable-__cxa_atexit--enable-clocale=gnu --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --enable-shared --enable-threads=posix --enable-multilib --disable-libgcj --enable-languages=c,c++ Thread model: posix gcc version 3.4.3 (Gentoo Hardened Linux 3.4.3, ssp-3.4.3-0, pie-8.7.6.6)
#1. There is no aoss32 on line 3 of /usr/games/bin/et #2. You will need 32-bit oss alsa support in your kernel #3. WORKSFORME #4. Don't post your whole make.conf, but rather the output of "emerge info" Anyway, the problem is obviously with your local ALSA configuration. The game is setup to work properly provided you have a properly configured kernel. I would bet your kernel is configured wrong. Check to ensure you have 32-bit OSS emulation enabled in your ALSA configuration and that you have alsa-lib installed.
I don't even have an aoss32 on my machine, only aoss. Do you have the emul-linux-x86-soundlibs installed? If so, what if you remove them?
I am going to REOPEN this since apparently some amd64 developer edited my ebuild without infomring me and caused this bug.
I have reverted the changes made to the ebuild, so the game should now work properly. Sorry about the confusion. It was my fault for not looking to see if someone had changed the ebuild without notifying me.
I didn't have emul-linux-x86-soundlibs installed installed. Installing it gave me this error insted: $ et /usr/bin/aoss32: line 7: exec: exec: not found I looks like a dep on emul-linux-x86-soundlibs is needed on AMD64 The new error is proberly not relatede to enemy-territory...
For one, do not reopen this bug. This bug was caused by a developer that was not familiar with the package making changes on the advice of a user that was not familiar with the workings of this package. I HAVE AN AMD64 MACHINE. There is no requirement for *any* emul-* libs other than xlibs to play this on amd64. As I stated before, I have reverted the ebuild. You need to perform a sync and re-install the ebuild. The developer did not take the care to test his changes. There is no binary called exec, as it is a bash function. Had the developer taken the time to test his changes to my ebuild, he would have noticed that "exec aoss32 et" would have been correct.
That's not the most polite treatement I been given... Maybe it will be a god idear to forbide you to talk to any one on bugzilla! This treamtement will not make the users report bugs... just make them change distro! You may be a good dev... but you are a bade person!
I'm sorry, but I don't understand. At no point was I even making a comment towards you. In fact, everything that I said was merely fact about the history of this ebuild. I honestly do not have a clue what you're talking about. If you look at comment #4, I had said that I had reverted the change. That would imply that I made a change to the portage tree, which would require you to emerge --sync and emerge enemy-territory again. I am sorry if I did not make that clear enough. As for not replying to bugs on bugzilla, I have no problem with that, at all. It just means that there won't be any fixes for bugs in games that I support.
