Sometimes I get the following message when emerging packages: stty: standard input: Invalid argument In some ebuilds this message shows many times (between compiler command lines), in others it does not appear at all. It doesn't seem to affect anything, just looks strange. Reproducible: Sometimes Steps to Reproduce: Unfortunately I don't know how to reproduce it, it just happens sometimes, but did not happen before.
Portage 2.0.46-r12 (default-x86-1.4, gcc-which: no gcc in (/sbin:/bin:/usr/sbin:/usr/bin) sh: line 1: -dumpversion: command not found, glibc-2.3.1-r2) ================================================================= System uname: 2.4.19-xfs-r2 i686 AMD Athlon(tm) MP 2000+ GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo/" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3/sh are/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quickti me spell truetype xmms xv zlib gdbm berkdb slang readline tetex svga tcltk java X sdl gpm tcpd libww w ssl python imlib oggvorbis gnome gtk motif opengl cdr gtk2 -qt -qtmt -kde -arts xfs acl bonobo enc ode aalib dga dvd gd alsa esd gtkhtml guile imap -ldap leim mozilla moznomail moznocompose moznoirc mysql pam perl scanner sse tiff xface xml2" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon-mp -O3 -pipe" CXXFLAGS="-mcpu=athlon-mp -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j3" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
my bet is that in your startup script (.cshrc or the like), your'e issuing an stty command without any notion of whether you're in an interactive shell or not. then, when portage does something in that shell, you try and perform an stty command, which fails because you're not in an interactive shell. try looking through your rc files for stty commands and guarding them with something like: # csh example if ($?prompt) then stty erase '^H' endif
You're right, my stty settings were in ~/.bashrc instead of ~/.bash_profile, that caused this error message, thanks! (Although I still don't understand why this happens only with some ebuilds and only since the latest portage update.)
glad to help. closing this.
