| View previous topic :: View next topic |
| Author |
Message |
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
 Posted: Wed Aug 21, 2002 2:06 am Post subject: serious emerge problem |
 |
|
sorry to bother everyone again, but i'm really desperately looking for a solution to this problem.
could someone please be so kind and help me out on this? thanks a lot.
I have already tried deleting the sandboxpids.tmp file, but this didn't solve it, wasn't a surprise actually since the error messages i get are quite different from the ones where deleting the sandboxpids.tmp file was the solution.
i've also tried to emerge -u "insert name of application" a number of applications seperately, but without any luck. the error messages displayed when emerge aborts differ with each app though.
i really can't figure out what's going on.
| Code: | root@tjb thomas # emerge -p -u system
These are the packages that I would merge, in order.
Calculating system dependencies ...done!
[ebuild U ] sys-apps/portage-2.0.28 to /
[ebuild U ] sys-devel/perl-5.6.1-r6 to /
[ebuild U ] net-misc/rsync-2.5.5-r1 to /
[ebuild U ] sys-apps/hdparm-5.2-r2 to /
[ebuild N ] sys-apps/iptables-1.2.7 to /
root@tjb thomas # emerge -u system
Calculating system dependencies ...done!
>>> emerge sys-apps/portage-2.0.28 to /
>>> Unpacking source...
>>> Source unpacked.
In file included from /usr/include/errno.h:36,
from tbz2tool.c:5:
/usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
gcc -O2 -march=i386 -fPIC -pipe sandbox.c -o sandbox
gcc -O2 -march=i386 -fPIC -pipe -c -o libsandbox.o libsandbox.c
In file included from /usr/include/errno.h:36,
from sandbox.c:19:
/usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
In file included from /usr/include/bits/posix1_lim.h:126,
from /usr/include/dirent.h:209,
from libsandbox.c:22:
/usr/include/bits/local_lim.h:36: linux/limits.h: No such file or directory
In file included from /usr/include/errno.h:36,
from libsandbox.c:24:
/usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
In file included from /usr/include/bits/posix1_lim.h:126,
from /usr/include/limits.h:144,
from
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include/limits.h:117,
from
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include/syslimits.h:7,
from
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/include/limits.h:11,
from sandbox.c:24:
/usr/include/bits/local_lim.h:36: linux/limits.h: No such file or directory
sandbox.c: In function `main':
sandbox.c:343: `PATH_MAX' undeclared (first use in this function)
sandbox.c:343: (Each undeclared identifier is reported only once
sandbox.c:343: for each function it appears in.)
sandbox.c:452: `ENOENT' undeclared (first use in this function)
sandbox.c:460: `EACCES' undeclared (first use in this function)
make: *** [sandbox] Error 1
make: *** Waiting for unfinished jobs....
libsandbox.c: In function `before_syscall':
libsandbox.c:843: `EACCES' undeclared (first use in this function)
libsandbox.c:843: (Each undeclared identifier is reported only once
libsandbox.c:843: for each function it appears in.)
make: *** [libsandbox.o] Error 1
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 4, Exitcode 2
!!! (no error message)
!!! emerge aborting on /usr/portage/sys-apps/portage/portage-2.0.28.ebuild .
root@tjb thomas # |
i'd really appreciate any help i can get. i've spent a lot of time building up my system (it actually still works great except for that serious problem with emerge) and starting from scretch is really not an option.
the only thing i can think of which i have done outside the ususal just before the problem started is, a while ago i had moved my /usr/portage folder to a different (also ext2) partition for lack of space and than created a link in / (this worked perfect and i never had any problem with emerge), but a couple days ago after changing the partition layout i have moved the /usr/portage folder back to /. could this be the reason for my problem, and if yes, does someone have a suggestion how i could solve it? thanks everyone for taking the time to read this.
best regards,
thomas. |
|
| Back to top |
|
 |
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 2:10 am Post subject: |
|
|
Could you try emerging linux-headers?
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
mihochan
Apprentice
Joined: 16 Apr 2002
Posts: 296
Location: Melbourne again
|
| Posted: Wed Aug 21, 2002 2:16 am Post subject: |
|
|
| Is gcc broken? |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 2:21 am Post subject: |
|
|
thanks for your fast reply rac! could you please let me know how i can try emerging linux-headers?
thanks mihochan for quick reply! i never messed around with gcc, and as far as i know gcc's files are not located in the /usr/portage folder (which i had moved around as mentioned) so i can't really see why it should be broken. how could i find out/test it though?
thanks,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 2:26 am Post subject: |
|
|
| thomasjb wrote: | | thanks for your fast reply rac! could you please let me know how i can try emerging linux-headers? |
What happens when you try: | Code: | | # emerge linux-headers |
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 2:36 am Post subject: |
|
|
sorry, wasn't aware that you can emerge linux-headers just like any other application.
just did it and it seems to have worked, emerge did not abort and finished as usual.
but when trying "emerge -u system" emerge still aborts with the following error message:
| Code: | root@tjb thomas # emerge -u system
Calculating system dependencies ...done!
>>> emerge sys-apps/portage-2.0.28 to /
>>> Unpacking source...
>>> Source unpacked.
gcc -O2 -march=i386 -fPIC -pipe sandbox.c -o sandbox
gcc -O2 -march=i386 -fPIC -pipe -c -o libsandbox.o libsandbox.c
gcc -O2 -march=i386 -fPIC -pipe libsandbox.o -o libsandbox.so -ldl --shared
>>> Install portage-2.0.28 into /var/tmp/portage/portage-2.0.28/image/ category
sys-apps
running install
running build
running build_ext
building 'missingos' extension
creating build
creating build/temp.linux-i686-2.2
gcc -DNDEBUG -march=i686 -O3 -pipe -fPIC -I/usr/include/python2.2 -c missingos.c
-o build/temp.linux-i686-2.2/missingos.o -march=i686 -O3 -pipe
missingos.c:1: Python.h: No such file or directory
missingos.c:9: parse error before `*'
missingos.c:9: parse error before `*'
missingos.c:9: warning: data definition has no type or storage class
missingos.c:11: parse error before `*'
missingos.c:11: parse error before `*'
missingos.c:11: warning: data definition has no type or storage class
missingos.c:16: parse error before `missingos_methods'
missingos.c:17: warning: braces around scalar initializer
missingos.c:17: warning: (near initialization for `missingos_methods[0]')
missingos.c:17: warning: initialization makes integer from pointer without a
cast
missingos.c:17: warning: excess elements in scalar initializer
missingos.c:17: warning: (near initialization for `missingos_methods[0]')
missingos.c:17: `METH_VARARGS' undeclared here (not in a function)
missingos.c:17: warning: excess elements in scalar initializer
missingos.c:17: warning: (near initialization for `missingos_methods[0]')
missingos.c:17: warning: excess elements in scalar initializer
missingos.c:17: warning: (near initialization for `missingos_methods[0]')
missingos.c:18: warning: braces around scalar initializer
missingos.c:18: warning: (near initialization for `missingos_methods[1]')
missingos.c:18: warning: initialization makes integer from pointer without a
cast
missingos.c:18: warning: excess elements in scalar initializer
missingos.c:18: warning: (near initialization for `missingos_methods[1]')
missingos.c:18: `METH_VARARGS' undeclared here (not in a function)
missingos.c:18: warning: excess elements in scalar initializer
missingos.c:18: warning: (near initialization for `missingos_methods[1]')
missingos.c:18: warning: excess elements in scalar initializer
missingos.c:18: warning: (near initialization for `missingos_methods[1]')
missingos.c:19: warning: braces around scalar initializer
missingos.c:19: warning: (near initialization for `missingos_methods[2]')
missingos.c:19: warning: initialization makes integer from pointer without a
cast
missingos.c:19: warning: excess elements in scalar initializer
missingos.c:19: warning: (near initialization for `missingos_methods[2]')
missingos.c:20: warning: data definition has no type or storage class
missingos.c:22: parse error before `*'
missingos.c: In function `posix_error_with_allocated_filename':
missingos.c:25: `PyObject' undeclared (first use in this function)
missingos.c:25: (Each undeclared identifier is reported only once
missingos.c:25: for each function it appears in.)
missingos.c:25: `rc' undeclared (first use in this function)
missingos.c:25: `PyExc_OSError' undeclared (first use in this function)
missingos.c: At top level:
missingos.c:34: parse error before `*'
missingos.c:35: parse error before `*'
missingos.c: In function `missingos_lchown':
missingos.c:39: `args' undeclared (first use in this function)
missingos.c:40: `Py_FileSystemDefaultEncoding' undeclared (first use in this
function)
missingos.c:47: `Py_None' undeclared (first use in this function)
missingos.c: At top level:
missingos.c:57: parse error before `*'
missingos.c:58: parse error before `*'
missingos.c: In function `missingos_mknod':
missingos.c:68: `args' undeclared (first use in this function)
missingos.c:69: `Py_FileSystemDefaultEncoding' undeclared (first use in this
function)
missingos.c:93: `PyExc_ValueError' undeclared (first use in this function)
missingos.c:106: `Py_None' undeclared (first use in this function)
missingos.c: At top level:
missingos.c:112: parse error before `initmissingos'
missingos.c: In function `initmissingos':
missingos.c:113: `PyObject' undeclared (first use in this function)
missingos.c:113: `m' undeclared (first use in this function)
missingos.c:116: parse error before `)'
missingos.c:117: `PYTHON_API_VERSION' undeclared (first use in this function)
error: command 'gcc' failed with exit status 1
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_install, Line -365, Exitcode 1
!!! (no error message)
!!! emerge aborting on /usr/portage/sys-apps/portage/portage-2.0.28.ebuild .
root@tjb thomas # |
it's a different error message than before. does it give you any hints on what's wrong?
thanks a lot for your patience!
regards,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 2:44 am Post subject: |
|
|
Wow - you really stuffed up your /usr/include directory somehow. Try re-emerging python.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 3:01 am Post subject: |
|
|
thanks rac! it's a mistery to me, never touched that directory ever.
emerging python seems to have worked. however, when trying to "emerge -u system", "emerge rsync" or "emerge portage" i now get the following error messages:
| Code: | root@tjb thomas # emerge -u system
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb thomas # emerge rsync
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb thomas # emerge portage
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb thomas # |
which is really strange, 'cause one thing that did still work before without flaw was "emerge rsync".
sorry for bothering you. do you have any suggestions?
thanks,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 3:16 am Post subject: |
|
|
| thomasjb wrote: | | do you have any suggestions? |
Oh yeah, I've always got suggestions. Problem is, a considerable number of them don't work, as you may have noticed. 
Somehow it looks like your Python got built without threading. I'm guessing that's because it couldn't find a thread-related header in that wasteland of a /usr/include that you're stuck with.
Do you have a stage tarball handy? Try moving your current /usr/include somewhere like /usr/include-steaming-pile-of-trash, and then: | Code: | # cd /
# tar xvjf stage.tbz2 usr/include |
...that should get your /usr/include into a clean state. Then remerge python (maybe linux-headers if /usr/include/linux is missing - the only stage tarball I've got sitting around here to check is a PPC stage 3, and that's probably not what you have). And then let's see where we are.
P.S. Just for fun, what does | Code: | | $ ldd /usr/bin/python | grep thr |
...say on your current python? I get | Quote: | | libpthread.so.0 => /lib/libpthread.so.0 (0x40025000) |
...but I'm betting you get nothing.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 3:54 am Post subject: |
|
|
you have the patience of a saint, rac! thanks!
you're exactly right, the "grep" command gave me nothing.
i still have the original stage tarball i installed gentoo from, and will try to extrct the "include" folder as suggested.
i'll let you know how far i got.
thanks for all your help!
regards,
thomas. |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 4:55 am Post subject: |
|
|
sorry, rac! didn't work. i extracted "usr/include" from the tar ball, no problem, but when i tried to emerge "linux-headers" and "python" again i get the following error messages:
| Code: | root@tjb home # emerge linux-headers
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb home # emerge phyton
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb home # |
i think now we are really stuck. is there any way to fix python?
regards,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 5:13 am Post subject: |
|
|
Were there any major differences between the /usr/include that came out of the stage tarball and the one you had moved out of the way before?
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 5:32 am Post subject: |
|
|
| yes. the "pile-of-trash" has 89 files/10 directories and the one from the original tarball has 143 files/37 directories. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 5:38 am Post subject: |
|
|
All right, this one could seriously hose your system if it doesn't work, so back up /home, important stuff in /etc, first. Keep or burn an install CD handy so you can always boot off of that. I figure if you can't emerge system, the install is not in good shape, so let's try remerging glibc. Maybe the python build is trying to run test programs against the threading libraries and failing.
After remerging glibc, on the next python try, see if you can figure out what's going on regarding threading when ebuild is running the configure stage.
If that doesn't work, I think we're pretty much at the point where you're better off saving everything you want to save and starting the install from scratch again. Sorry. 
Of course, after I post this, Naan Yaar will probably come along with a one-line script that solves everything immediately.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 5:49 am Post subject: |
|
|
| thanks a lot, rac. that sounds quite scary though. strange thing is, except for emerge everything seems to work fine on my system. i'm a bit worried about screwing it up totally. i'll try to remerge glibc and let you how how i went. |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 6:21 am Post subject: |
|
|
sorry, didn't work.
| Code: | root@tjb home # emerge glibc
Traceback (most recent call last):
File "/usr/bin/emerge", line 2, in ?
import os,sys,portage,xpak,string,re,commands,time,threading,shutil
File "/usr/lib/python2.2/threading.py", line 5, in ?
import thread
ImportError: No module named thread
root@tjb home # |
same error message as when trying to emerge "linux-headers" and "python".
it looks like i will be able to use my system as is as long as i want ( as mentioned before, everything else works fine), but everything "emerge" related won't work anymore.
thanks for your patience and your help rac, i really appreciate it.
regards,
thomas. |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 6:40 am Post subject: |
|
|
sorry, but i have not given up yet. i downloaded the "python" sources from the "python" homepage and tried to install them "by hand" this is the result:
| Code: | bash-2.05a$ ./configure
creating cache ./config.cache
checking MACHDEP... linux2
checking for --without-gcc... no
checking for --with-cxx=<compiler>... no
checking for c++... c++
checking whether the C++ compiler (c++ ) works... yes
checking whether the C++ compiler (c++ ) is a cross-compiler... no
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for AIX... no
checking for minix/config.h... no
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for executable suffix... no
checking for --with-suffix...
checking for case-insensitive build directory... no
checking LIBRARY... libpython$(VERSION).a
checking LINKCC... $(PURIFY) $(CC)
checking LDLIBRARY... libpython$(VERSION).a
checking for ranlib... ranlib
checking for ar... ar
checking for a BSD compatible install... /bin/install -c
checking for --with-pydebug... no
checking whether gcc accepts -OPT:Olimit=0... no
checking whether gcc accepts -Olimit 1500... no
checking whether pthreads are available without options... no
checking whether gcc accepts -Kpthread... no
checking for ANSI C header files... yes
checking for dlfcn.h... yes
checking for fcntl.h... yes
checking for grp.h... yes
checking for limits.h... no
checking for langinfo.h... yes
checking for locale.h... yes
checking for ncurses.h... yes
checking for poll.h... yes
checking for pthread.h... yes
checking for signal.h... yes
checking for stdarg.h... yes
checking for stddef.h... yes
checking for stdlib.h... yes
checking for thread.h... no
checking for unistd.h... yes
checking for utime.h... yes
checking for termios.h... yes
checking for sys/audioio.h... no
checking for sys/file.h... yes
checking for sys/lock.h... no
checking for sys/modem.h... no
checking for db_185.h... no
checking for db.h... yes
checking for sys/param.h... no
checking for sys/poll.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... no
checking for sys/time.h... yes
checking for sys/times.h... yes
checking for sys/un.h... yes
checking for sys/utsname.h... yes
checking for sys/wait.h... yes
checking for pty.h... yes
checking for term.h... yes
checking for libutil.h... no
checking for ndbm.h... no
checking for db1/ndbm.h... no
checking for gdbm/ndbm.h... yes
checking for sys/resource.h... yes
checking for netpacket/packet.h... yes
checking for dirent.h that defines DIR... no
checking for sys/ndir.h that defines DIR... no
checking for sys/dir.h that defines DIR... no
checking for ndir.h that defines DIR... no
checking for opendir in -lx... no
checking for clock_t in time.h... yes
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking return type of signal handlers... void
checking for size_t... yes
checking for uid_t in sys/types.h... yes
checking size of int... 4
checking size of long... 4
checking size of void *... 4
checking size of char... 1
checking size of short... 2
checking size of float... 4
checking size of double... 8
checking size of fpos_t... 16
checking for long long support... yes
checking size of long long... 8
checking for uintptr_t support... no
checking size of off_t... 8
checking whether to enable large file support... yes
checking size of time_t... 4
checking for pthread_t... yes
checking size of pthread_t... 4
checking for --enable-toolbox-glue... no
checking for --enable-framework... no
checking for dyld... no
checking SO... .so
checking LDSHARED... gcc -shared
checking CCSHARED... -fPIC
checking LINKFORSHARED... -Xlinker -export-dynamic
checking CFLAGSFORSHARED...
checking for dlopen in -ldl... yes
checking for shl_load in -ldld... no
checking for t_open in -lnsl... no
checking for socket in -lsocket... no
checking for --with-libs... no
checking for --with-signal-module... yes
checking for --with-dec-threads... no
checking for --with-threads... yes
checking for _POSIX_THREADS in unistd.h... yes
checking for mach/cthreads.h... no
checking for --with-pth... no
checking for pthread_create in -lpthread... yes
checking if PTHREAD_SCOPE_SYSTEM is supported... yes
checking for pthread_sigmask... yes
checking for usconfig in -lmpc... no
checking for thr_create in -lthread... no
checking if --enable-ipv6 is specified... no
checking for --with-cycle-gc... yes
checking for --with-pymalloc... no
checking for --with-wctype-functions... no
checking for --with-sgi-dl... no
checking for --with-dl-dld... no
checking for dlopen... yes
checking DYNLOADFILE... dynload_shlib.o
checking MACHDEP_OBJS... MACHDEP_OBJS
checking for alarm... yes
checking for chown... yes
checking for chroot... yes
checking for clock... yes
checking for confstr... yes
checking for ctermid... yes
checking for ctermid_r... no
checking for execv... yes
checking for flock... yes
checking for fork... yes
checking for fsync... yes
checking for fdatasync... yes
checking for fpathconf... yes
checking for ftime... yes
checking for ftruncate... yes
checking for gai_strerror... yes
checking for getgroups... yes
checking for getlogin... yes
checking for getpeername... yes
checking for getpid... yes
checking for getpwent... yes
checking for getwd... yes
checking for hstrerror... yes
checking for inet_pton... yes
checking for kill... yes
checking for link... yes
checking for lstat... yes
checking for mkfifo... yes
checking for mktime... yes
checking for mremap... yes
checking for nice... yes
checking for pathconf... yes
checking for pause... yes
checking for plock... no
checking for poll... yes
checking for pthread_init... no
checking for putenv... yes
checking for readlink... yes
checking for select... yes
checking for setegid... yes
checking for seteuid... yes
checking for setgid... yes
checking for setgroups... yes
checking for setlocale... yes
checking for setregid... yes
checking for setreuid... yes
checking for setsid... yes
checking for setpgid... yes
checking for setuid... yes
checking for setvbuf... yes
checking for snprintf... yes
checking for sigaction... yes
checking for siginterrupt... yes
checking for sigrelse... yes
checking for strftime... yes
checking for strptime... yes
checking for symlink... yes
checking for sysconf... yes
checking for tcgetpgrp... yes
checking for tcsetpgrp... yes
checking for tempnam... yes
checking for timegm... yes
checking for times... yes
checking for tmpfile... yes
checking for tmpnam... yes
checking for tmpnam_r... yes
checking for truncate... yes
checking for uname... yes
checking for unsetenv... yes
checking for waitpid... yes
checking for _getpty... no
checking for getpriority... yes
checking for openpty... no
checking for openpty in -lutil... yes
checking for forkpty... yes
checking for fseek64... no
checking for fseeko... yes
checking for fstatvfs... yes
checking for ftell64... no
checking for ftello... yes
checking for statvfs... yes
checking for dup2... yes
checking for getcwd... yes
checking for strdup... yes
checking for strerror... yes
checking for memmove... yes
checking for getpgrp... yes
checking for setpgrp... yes
checking for gettimeofday... yes
checking for getaddrinfo... no
checking for getnameinfo... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for tm_zone in struct tm... yes
checking for st_rdev in struct stat... yes
checking for st_blksize in struct stat... yes
checking for st_blocks in struct stat... yes
checking for time.h that defines altzone... no
checking whether sys/select.h and sys/time.h may both be included... yes
checking for addrinfo... no
checking for sockaddr_storage... no
checking whether char is unsigned... no
checking for working const... yes
checking for working volatile... yes
checking for working signed char... yes
checking for prototypes... yes
checking for variable length prototypes and stdarg.h... yes
checking for bad exec* prototypes... no
checking if sockaddr has sa_len member... no
checking for bad static forward... no
checking whether va_list is an array... no
checking for gethostbyname_r... yes
checking gethostbyname_r with 6 args... no
checking gethostbyname_r with 5 args... no
checking gethostbyname_r with 3 args... no
checking for __fpu_control... yes
checking for --with-fpectl... no
checking for --with-libm=STRING... default LIBM="-lm"
checking for --with-libc=STRING... default LIBC=""
checking for hypot... yes
checking what malloc(0) returns... null
checking for wchar.h... yes
checking size of wchar_t... 4
checking what type to use for unicode... unsigned short
checking whether byte ordering is bigendian... no
checking whether right shift extends the sign bit... yes
checking for getc_unlocked() and friends... yes
checking for rl_pre_input_hook in -lreadline... no
checking for rl_completion_matches in -lreadline... no
checking for broken nice()... yes
checking whether mvwdelch is an expression... yes
checking whether WINDOW has _flags... yes
checking for socklen_t... no
checking for build directories... done
updating cache ./config.cache
creating ./config.status
creating Makefile.pre
creating Modules/Setup.config
creating pyconfig.h
creating Setup
creating Setup.local
creating Makefile
bash-2.05a$ make
gcc -c -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -I./Include -DHAVE_CONFIG_H
-o Modules/python.o Modules/python.c
In file included from /usr/include/errno.h:36,
from Include/Python.h:48,
from Modules/python.c:3:
/usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
make: *** [Modules/python.o] Error 1
bash-2.05a$
|
sorry for posting the whole thing, but is there any usefull information in there pointing to what the exact problem is and how to resolve it?
regards,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 6:47 am Post subject: |
|
|
That is sounding familiar. Does /usr/include/linux/errno.h exist? It should be part of kernel-headers. I'm working on another post for how to get a binary python package out of the stage tarball - hang on a minute.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 6:52 am Post subject: |
|
|
| thomasjb wrote: | | it looks like i will be able to use my system as is as long as i want ( as mentioned before, everything else works fine), but everything "emerge" related won't work anymore. |
Oh yeah, python is still unhappy.
OK, I'm not done yet.
Step 1. Figure out what files are supposed to belong to python. I don't trust your live python any more, so break out that stage tarball again. Use something like | Code: | | $ tar tjf stage.tbz2 | grep python | grep CONTENTS |
You are looking for the CONTENTS file for the python build. It should be in var/db/pkg/dev-lang/python-version, probably. Extract it somewhere out of that stage tarball like you did with usr/include; anywhere is fine. Just that one file. I'll assume it's in /tmp/python.contents. Now | Code: | | $ cat /tmp/python.contents | awk {print $2} > /tmp/python-files |
...and you should have a nice list of python files.
Step 2. Grab those out of the stage tarball and overwrite your python installation. | Code: | # cd /
# tar xvjf stage.tgz -T /tmp/python-files |
That will hopefully fix python. Then try emerging glibc.
I haven't actually tested any of this, so there might be stupid typos.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 7:25 am Post subject: |
|
|
it's getting really confusing. checked on "/usr/include/linux/errno.h", it did not exist in the "include" i extracted from the tarball; for some reason though it did exist in the "pile-of-trash" version of "include".
working on your suggestion to recreate "python"
thanks,
thomas. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 7:29 am Post subject: |
|
|
| thomasjb wrote: | | it's getting really confusing. checked on "/usr/include/linux/errno.h", it did not exist in the "include" i extracted from the tarball; for some reason though it did exist in the "pile-of-trash" version of "include". |
Actually that does make some sense; the linux-headers must not be included in the stage tarball. So you may need to copy those directories with "cp -R" from the pile-of-trash to /usr/include or reemerge linux-headers if python comes back to life.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 8:39 am Post subject: |
|
|
worked my way through recreating python. still can't do anything with the "emerge" command however the "grep" command concerning "python" does produce an output now.
| Code: | root@tjb thomas # ldd /usr/bin/python | grep thr
libpthread.so.0 => /lib/libpthread.so.0 (0x40028000)
root@tjb thomas # emerge rsync
Traceback (most recent call last):
File "/usr/bin/emerge", line 295, in ?
portage.portdb.freeze()
AttributeError: 'module' object has no attribute 'portdb'
root@tjb thomas # emerge linux-headers
Traceback (most recent call last):
File "/usr/bin/emerge", line 295, in ?
portage.portdb.freeze()
AttributeError: 'module' object has no attribute 'portdb'
root@tjb thomas # emerge python
Traceback (most recent call last):
File "/usr/bin/emerge", line 295, in ?
portage.portdb.freeze()
AttributeError: 'module' object has no attribute 'portdb'
root@tjb thomas # |
did we make headway here? |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Aug 21, 2002 8:45 am Post subject: |
|
|
| thomasjb wrote: | | did we make headway here? |
Well, one of my mottos is "changing error messages often indicate progress". I think the next move is to try to use one of the Portage rescue tarballs. See instructions in /usr/portage/sys-apps/portage/files/README.RESCUE.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
thomasjb
Apprentice
Joined: 26 May 2002
Posts: 176
Location: Beijing
|
| Posted: Wed Aug 21, 2002 1:29 pm Post subject: |
|
|
after using a "portage" rescue tarball i was able to "emerge rsync" as well as "emerge -u" "portage" and a few other apps. it seems to work now again apart from not being able to "emerge -u rsync" which aborts with the following error message:
| Quote: | ...
options.c:363: warning: (near initialization for `long_options[68]')
options.c:363: warning: excess elements in struct initializer
options.c:363: warning: (near initialization for `long_options[68]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: `POPT_ARG_VAL' undeclared here (not in a function)
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:365: warning: excess elements in struct initializer
options.c:365: warning: (near initialization for `long_options[69]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: `POPT_ARG_VAL' undeclared here (not in a function)
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:366: warning: excess elements in struct initializer
options.c:366: warning: (near initialization for `long_options[70]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:368: warning: excess elements in struct initializer
options.c:368: warning: (near initialization for `long_options[71]')
options.c:369: invalid use of undefined type `struct poptOption'
options.c: In function `check_refuse_options':
options.c:398: invalid use of undefined type `struct poptOption'
options.c:399: invalid use of undefined type `struct poptOption'
options.c:402: invalid use of undefined type `struct poptOption'
options.c:404: invalid use of undefined type `struct poptOption'
options.c: In function `parse_arguments':
options.c:438: `poptContext' undeclared (first use in this function)
options.c:438: (Each undeclared identifier is reported only once
options.c:438: for each function it appears in.)
options.c:438: parse error before `pc'
options.c:444: `pc' undeclared (first use in this function)
options.c:444: warning: implicit declaration of function `poptGetContext'
options.c:446: warning: implicit declaration of function `poptGetNextOpt'
options.c:472: warning: implicit declaration of function `poptGetOptArg'
options.c:472: warning: passing arg 1 of `add_exclude' makes pointer from
integer without a cast
options.c:476: warning: passing arg 1 of `add_exclude' makes pointer from
integer without a cast
options.c:480: warning: passing arg 1 of `add_exclude_file' makes pointer from
integer without a cast
options.c:484: warning: passing arg 1 of `add_exclude_file' makes pointer from
integer without a cast
options.c:572: warning: implicit declaration of function `poptBadOption'
options.c:572: `POPT_BADOPTION_NOALIAS' undeclared (first use in this function)
options.c:573: warning: implicit declaration of function `poptStrerror'
options.c:573: warning: format argument is not a pointer (arg 5)
options.c:573: warning: format argument is not a pointer (arg 6)
options.c:594: warning: implicit declaration of function `poptGetArgs'
options.c:594: warning: assignment makes pointer from integer without a cast
make: *** [options.o] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 10, Exitcode 2
!!! (no error message)
!!! emerge aborting on /usr/portage/net-misc/rsync/rsync-2.5.5-r1.ebuild .
root@tjb thomas #
|
and the fact that i somehow messed up my mail folder (mozilla) and made my bookmarks (mozilla) disapear. very strange.
again, thanks a lot for all your help, rac. i really appreciate your time and patience. thanks!
regards,
thomas. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
