after installation, the programm just cant run: # file /usr/bin/gcc-config /usr/bin/gcc-config: data # /usr/bin/gcc-config bash: /usr/bin/gcc-config: cannot execute binary file Reproducible: Always Steps to Reproduce: 1. rm /usr/bin/gcc-config 2. emerge gcc-config 3. gcc-config Actual Results: cannot execute binary file Expected Results: bah ... I ve never seen it working ... I am not sure what it should produce :/ echo "FEATURES=\"noclean -clean\"" >> /etc/make.conf # emerge -v gcc-config Calculating dependencies ...done! >>> emerge (1 of 1) sys-devel/gcc-config-1.3.10-r2 to / >>> Unpacking source... >>> Source unpacked. >>> Test phase [not enabled]: sys-devel/gcc-config-1.3.10-r2 >>> Install gcc-config-1.3.10-r2 into /var/tmp/portage/gcc-config-1.3.10-r2/image/ category sys-devel man: prepallstrip: strip: strip --strip-unneeded strip: strip --strip-unneeded usr/lib/misc/gcc-config >>> Completed installing gcc-config-1.3.10-r2 into /var/tmp/portage/gcc-config-1.3.10-r2/image/ >>> Merging sys-devel/gcc-config-1.3.10-r2 to / --- /usr/ --- /usr/bin/ >>> /usr/bin/gcc-config --- /usr/lib/ --- /usr/lib/misc/ >>> /usr/lib/misc/gcc-config >>> Safely unmerging already-installed instance... --- !mtime obj /usr/lib/misc/gcc-config --- !mtime obj /usr/bin/gcc-config --- !empty dir /usr/lib/misc --- !empty dir /usr/lib --- !empty dir /usr/bin --- !empty dir /usr >>> original instance of package unmerged safely. >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... >>> sys-devel/gcc-config-1.3.10-r2 merged. >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. /var/tmp is a symlink to /home/var_tmp. root@pluton:/home/var_tmp/portage# file /usr/bin/gcc-config /usr/bin/gcc-config: data root@pluton:/home/var_tmp/portage# file /var/tmp/portage/gcc-config-1.3.10-r2/temp/gcc-config /var/tmp/portage/gcc-config-1.3.10-r2/temp/gcc-config: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not stripped root@pluton:/home/var_tmp/portage# cp /var/tmp/portage/gcc-config-1.3.10-r2/temp/gcc-config /usr/bin/gcc-config root@pluton:/home/var_tmp/portage# file /usr/bin/gcc-config /usr/bin/gcc-config: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not stripped root@pluton:/home/var_tmp/portage# strip /usr/bin/gcc-config root@pluton:/home/var_tmp/portage# file /usr/bin/gcc-config /usr/bin/gcc-config: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), stripped # emerge -vp gcc-config These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-devel/gcc-config-1.3.10-r2 0 kB Total size of downloads: 0 kB What else to say ?
/usr/bin/gcc-config should not be a binary file, it should just be a bash script does it work if you `emerge sync && emerge gcc-config` ? if not, what does `file /usr/portage/sys-devel/gcc-config/files/gcc-config*` show ?
Looks like my email was not added in this thread, lets repast in case ... >> /usr/bin/gcc-config should not be a binary file, it should just be a bash script I have been told so, on IRC ... >> does it work if you `emerge sync && emerge gcc-config` ? no. >> if not, what does `file /usr/portage/sys-devel/gcc-config/files/gcc-config*` show ? $ file /usr/portage/sys-devel/gcc-config/files/gcc-config* /usr/portage/sys-devel/gcc-config/files/gcc-config-1.3.10: data /usr/portage/sys-devel/gcc-config/files/gcc-config-1.3.8: data /usr/portage/sys-devel/gcc-config/files/gcc-config-1.4.0: data just to let you believe in me: $ file /etc/init.d/sshd /etc/init.d/sshd: a /sbin/runscript script text executable => `file` itself can still make the difference between an ELF, a script, and raw DATA :) when I vim /usr/portage/sys-devel/gcc-config/files/gcc-config-1.3.10: ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ what are 0x00 IIRC.
your portage tree is messed up maybe bad rsync or your system needs a fsck or your system had a fsck and it messed up your portage tree try `rm -r /usr/portage/sys-devel && emerge sync && emerge gcc-config`
