Summary: | /bin/sh: /bin/sed: cannot execute binary file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | baso <andreabaso> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
baso
2005-12-08 13:39:29 UTC
This question appears to be more apropriate for the forums or mailing lists. Have you tried reemerging sed? emerge sys-apps/sed Do the checksum match? equery check sys-apps/sed From the information you give, noone could diagnose the problem. See above... tux baso # emerge sed
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/sed-4.1.4 to /
>>> md5 files ;-) sed-4.1.4.ebuild
>>> md5 files ;-) sed-4.0.9.ebuild
>>> md5 files ;-) files/dos2unix
>>> md5 files ;-) files/unix2dos
>>> md5 files ;-) files/sed-4.1.4-makeinfo-c-locale.patch
>>> md5 files ;-) files/sed-4.1.4-fix-invalid-ref-error.patch
>>> md5 files ;-) files/digest-sed-4.0.9
>>> md5 files ;-) files/digest-sed-4.1.4
>>> md5 src_uri ;-) sed-4.1.4.tar.gz
>>> Unpacking source...
>>> Unpacking sed-4.1.4.tar.gz to /var/tmp/portage/sed-4.1.4/work
* Applying sed-4.1.4-makeinfo-c-locale.patch ... [ ok ]
* Applying sed-4.1.4-fix-invalid-ref-error.patch ... [ ok
]/usr/portage/sys-apps/sed/sed-4.1.4.ebuild: line 43: /bin/sed: cannot execute
binary file
!!! ERROR: sys-apps/sed-4.1.4 failed.
!!! Function src_unpack, Line 45, Exitcode 126
!!! sed html doc
!!! If you need support, post the topmost build error, NOT this status message.
tux baso # equery check sys-apps/sed
[ Checking sys-apps/sed-4.1.4 ]
!!! /usr/share/locale/da/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/html/sed.html has wrong mtime (is 1133993370, shoul
d be 1133286420)
!!! /usr/share/locale/he/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/README.gz has incorrect md5sum
!!! /usr/share/locale/pl/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/README-alpha.gz has incorrect md5sum
!!! /usr/share/locale/nl/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/examples/unix2dos.gz has incorrect md5sum
!!! /usr/share/locale/gl/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/sk/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/BUGS.gz has incorrect md5sum
!!! /usr/share/locale/eo/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/doc/sed-4.1.4/AUTHORS.gz has incorrect md5sum
!!! /usr/share/locale/el/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/info/sed.info.gz has incorrect md5sum
!!! /usr/share/man/man1/sed.1.gz has incorrect md5sum
!!! /usr/share/locale/it/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/es/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/hu/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/ru/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/af/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/sr/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/sl/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/et/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/ja/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/ca/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/fi/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/tr/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/hr/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/fr/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/id/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/ga/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/ro/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/zh_CN/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, s
hould be 1133286420)
!!! /usr/share/doc/sed-4.1.4/NEWS.gz has incorrect md5sum
!!! /bin/sed has incorrect md5sum
!!! /usr/share/doc/sed-4.1.4/examples/dos2unix.gz has incorrect md5sum
!!! /usr/share/locale/ko/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/pt_BR/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, s
hould be 1133286420)
!!! /usr/share/doc/sed-4.1.4/THANKS.gz has incorrect md5sum
!!! /usr/share/doc/sed-4.1.4/README.boot.gz has incorrect md5sum
!!! /usr/share/doc/sed-4.1.4/ChangeLog.gz has incorrect md5sum
!!! /usr/share/locale/cs/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/de/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
!!! /usr/share/locale/sv/LC_MESSAGES/sed.mo has wrong mtime (is 1133993370, shou
ld be 1133286420)
* 75 out of 120 files good
Your sed is apparently b0rked...
> !!! /bin/sed has incorrect md5sum
USE=bootstrap emerge sed && emerge sed
tux baso # USE="bootstrap" emerge sed && emerge sed
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/sed-4.1.4 to /
>>> md5 files ;-) sed-4.1.4.ebuild
>>> md5 files ;-) sed-4.0.9.ebuild
>>> md5 files ;-) files/dos2unix
>>> md5 files ;-) files/unix2dos
>>> md5 files ;-) files/sed-4.1.4-makeinfo-c-locale.patch
>>> md5 files ;-) files/sed-4.1.4-fix-invalid-ref-error.patch
>>> md5 files ;-) files/digest-sed-4.0.9
>>> md5 files ;-) files/digest-sed-4.1.4
>>> md5 src_uri ;-) sed-4.1.4.tar.gz
>>> Unpacking source...
>>> Unpacking sed-4.1.4.tar.gz to /var/tmp/portage/sed-4.1.4/work
* Applying sed-4.1.4-makeinfo-c-locale.patch ... [ ok ]
* Applying sed-4.1.4-fix-invalid-ref-error.patch ... [ ok ]
/usr/portage/sys-apps/sed/sed-4.1.4.ebuild: line 43: /bin/sed: cannot execute bi
nary file
!!! ERROR: sys-apps/sed-4.1.4 failed.
!!! Function src_unpack, Line 45, Exitcode 126
!!! sed html doc
!!! If you need support, post the topmost build error, NOT this status message.
I'm sorry, but your sed is screwed. Get a working binary somewhere and then re-emerge sed, rather than reopening this bug over and over again. There's nothing we could do for you if even 'USE=bootstrap emerge sed' does not work for you. This is not a bug, we did not break your binary. CLOSED I'm sorry to insist on this problem but I don't know what to do to resolve it because I got a working binary but when I ./configure it this is the output: tux sed-4.1.4 # ./configure ./configure: line 249: /bin/sed: cannot execute binary file ./configure: line 742: /bin/sed: cannot execute binary file ./configure: line 1004: /bin/sed: cannot execute binary file ./configure: line 1293: /bin/sed: cannot execute binary file checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... configure: error: ls -t appears to fail. Make sure there is not a broken alias in your environment configure: error: newly created file is older than distributed files! Check your system clock ./configure: line 1504: /bin/sed: cannot execute binary file ./configure: line 1546: /bin/sed: cannot execute binary file (In reply to comment #8) > configure: error: newly created file is older than distributed files! Your system clock sucks, fix it. My system clock has no problems I've searched but can't find a fix for this (In reply to comment #10) > My system clock has no problems Ah, sure... So the timestamps from future are caused by what? > configure: error: newly created file is older than distributed files! Once again - bugzilla is for bugs. Your broken sed and your incorrectly set system clock is not a bug. Get a working binary package for sed... If you still have questions, then direct them to forums.gentoo.org. Thanks. . Download the statically compiled sed to ${PKGDIR}/All and run emerge -K sed or just unpack it to / wget http://dev.gentoo.org/~jakub/sed-4.1.4.tbz2 |