I'm trying to setup virtualenvwrapper on OSX, and all the instructions and tutorials I've found tell me to add a source command to.profile, pointing towards virtualenvwrapper.sh. I've checked all the python and site-packages directories, and I can't find any virtualenvwrapper.sh. Is this something I need to download separately?
- No Such File Or Directory
- Stdio.h No Such File Or Directory
- Sqlstate Hy000 2002 No Such File Or Directory
Is pip not installing correctly? This is the contents of /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/virtualenvwrapper: hookloader.py hookloader.pyc project.py project.pyc userscripts.py userscripts.pyc As you can see, no virtualenvwrapper.sh. The exact path where virtualenvwrapper.sh is stored/located varies from OS to OS. Even with in same OS, it varies from version to version. So we need a generic solution that works for all OS versions. Easiest way I have found to find its path is: Do pip uninstall virtualenvwrapper This will prompt a confirmation.
Say 'No' But first line of confirmation shows the path of virtualenvwrapper.sh (Prompt gives a list of files it will delete, if you say Yes. First entry in this list contains path to virtualenvwrapper.sh in your machine). In OSx EI captain, I installed the virtualenvwrapper as sudo pip3 install virtualenvwrapper, however I cannot find the virtualenvwrapper.sh in /user/local/bin, it was finally found at /Library/Frameworks/Python.framework/Versions/3.4/bin/virtualenvwrapper.sh, and you can make an soft link to /usr/local/bin as ln -s /Library/Frameworks/Python.framework/Versions/3.4/bin/virtualenvwrapper.sh /usr/local/bin/virtualenvwrapper.sh, and everything you can just follow the setup guide as the official document does.
I've tried everything I can but now I need help! I've hit the limit of what I do understand.
My error: andytmac: admin$ lsvirtualenv andytmac: admin$ mkvirtualenv test -bash: /usr/local/bin/virtualenv: /usr/bin/python: bad interpreter: No such file or directory My take is that virtualenv doesn't know where python is. Is this the case? How can I fix this? System is Mac OSX 10.9.4 I have used brew to install python 2.7.8.1.
Python 2.7.something. was on there but I removed it.
I can't remember exactly what I did to do that however. I am new to macs.
In my case, I had previously installed virtualenvwrapper using apt-get install virtualenvwrapper and later uninstalled it using apt-get remove virtualenvwrapper, which left the 'configuration' file /etc/bashcompletion.d/virtualenvwrapper behind. This bash completion definition was sourced by bash (it had nothing to do with my.bashrc) and caused the error message. The solution was to run: sudo apt-get purge virtualenvwrapper Which purged all files related to virtualenvwrapper. The reason I uninstalled it was to use pip's version instead (more up-to-date), which can be installed globally using: sudo pip install virtualenvwrapper. Following, I found that the error occurred when sourcing the virtualenvwrapper bash script, i.e.: source /usr/local/bin/virtualenvwrapper.sh The script references the file /etc/bashcompletion.d/virtualenvwrapper as pointed out by arcticfeather. Open up the script using the following command: sudo nano /etc/bashcompletion.d/virtualenvwrapper This is where the non-existent file is being referenced.
Simply replace /usr/share/virtualenvwrapper/virtualenvwrapperlazy.sh with /usr/local/bin/virtualenvwrapperlazy.sh and you should be good to go!
Mv -f /sources/glibc-build/tls.makeT /sources/glibc-build/tls.make make1: Leaving directory `/sources/glibc-2.3.4' make1: Entering directory `/sources/glibc-2.3.4' make -C csu tests make2: Entering directory `/sources/glibc-2.3.4/csu' make2:. No rule to make target `/sources/glibc-build/csu/tst-empty.out', needed by `tests'.
No Such File Or Directory
Make2: Leaving directory `/sources/glibc-2.3.4/csu' make1:. csu/tests Error 2 make1: Leaving directory `/sources/glibc-2.3.4' make:. check Error 2root:/sources/glibc-build# touch /etc/ld.so.conf root:/sources/glibc-build# make install.
Make4: Entering directory `/sources/glibc-2.3.4/stdlib' make4: Nothing to be done for `rtld-all'. Make4: Leaving directory `/sources/glibc-2.3.4/stdlib' make -C./string objdir=/sources/glibc-build -f Makefile -f./elf/rtld-Rules rtld-all rtld-modules='rtld-strchr.os rtld-strcmp.os rtld-strlen.os rtld-strnlen.os rtld-memchr.os rtld-memmove.os rtld-memset.os rtld-mempcpy.os rtld-stpcpy.os rtld-memcpy.os' make4: Entering directory `/sources/glibc-2.3.4/string' make4: Nothing to be done for `rtld-all'.
Make4: Leaving directory `/sources/glibc-2.3.4/string' make -C./time objdir=/sources/glibc-build -f Makefile -f./elf/rtld-Rules rtld-all rtld-modules='rtld-setitimer.os' make4: Entering directory `/sources/glibc-2.3.4/time' make4: Nothing to be done for `rtld-all'. Make4: Leaving directory `/sources/glibc-2.3.4/time' make3: Leaving directory `/sources/glibc-2.3.4/elf' make2:. No rule to make target `/sources/glibc-build/dlfcn/libdl.so.2', needed by `/sources/glibc-build/elf/sprof'.Stop. Make2: Leaving directory `/sources/glibc-2.3.4/elf' make1:. elf/subdirinstall Error 2 make1: Leaving directory `/sources/glibc-2.3.4' make:. install Error 2root:/sources/glibc-build# mkdir -p /usr/lib/locale root:/sources/glibc-build# localedef -i deDE -f ISO-8859-1 deDE. Make2:.
No rule to make target `/sources/glibc-build/csu/tst-empty.out', needed by `tests'. It looks like glibc never finished building. When you did the 'make', did you get an error at the end? Did you start with a clean directory? (I remember from the other thread that you had a glibc-build directory sitting around somewhere. I hope you didn't reuse it. If so, delete glibc-2.3.4 and glibc-build, and start over.) In the future, if you get errors, don't plow ahead anyway.
Try to fix the error first. Code: chroot '$LFS' /tools/bin/env -i HOME=/root TERM='$TERM' PS1=' u: w $ ' PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin /tools/bin/bash -login +h The +h turns off bash's 'hashing' feature, which is a way that bash remembers where it found commands in the past. It found 'localedef' in /usr/bin at some point in the past, and it remembered that, so it isn't searching the $PATH for it again. To make it do that, do a hash -r to clear the hash, and then do a set +h to turn off hashing for the rest of the session. (Or just exit the chroot and re-enter it, either way.).
Code: total 12 drwxr-xr-x 2 root root 4096 Jul 27 09:14. Drwxr-xr-x 21 root root 4096 Jul 27 09:15. Yes, this is intended. This is not your Fedora partition's /mnt directory. This is your LFS partition's /mnt directory. The root directory, after chroot, is what you saw as Fedora's /mnt/lfs directory. So this /mnt that you're listing is really what Fedora sees as /mnt/lfs/mnt.
Stdio.h No Such File Or Directory
Which, if you look in another terminal (or Konqueror) is empty. Sorry, I'm not really sure how to make it more clear. Code: /tools/bin/localedef /usr/bin/localedefThere are 2 here Yes. That's because as the 'lfs' user, /tools/bin is in your $PATH, so the shell will look in there (and it finds a localedef). As any other user, however, it won't (because the other user's $PATH doesn't contain /tools/bin). However, I don't think localedef should be your immediate concern.
Your immediate concern should probably be why glibc is failing to finish testing or installing. Get that fixed first, and then (after it's been installed completely, with no errors) retry the localedef stuff. If you're getting an error from glibc's make, post it. The +h turns off bash's 'hashing' feature, which is a way that bash remembers where it found commands in the past. It found 'localedef' in /usr/bin at some point in the past, and it remembered that, so it isn't searching the $PATH for it again.
To make it do that, do a hash -r to clear the hash, and then do a set +h to turn off hashing for the rest of the session. (Or just exit the chroot and re-enter it, either way.) Sorry, I can't catch. Whether you meant re-run 'chroot' the second time? Code: glibc-2.3.4-fixtest-1.patch glibc-2.3.4-fixtest-1.patch.rej glibc-2.3.4.tar.bz2.orig glibc-2.3.4-fixtest-1.patch.orig glibc-2.3.4.tar.bz2 glibc-2.3.4.tar.bz2.rejRemark: I re-downloaded both 'glibc-2.3.4-fixtest-1.patch' and 'glibc-2.3.4.tar.bz2' Re-named the old ones as.orig glibc-2.3.4-fixtest-1.patch.rej glibc-2.3.4.tar.bz2.rej I have no idea how these files coming to existence. I left them there. Root:/sources# tar xjf glibc-2.3.4.tar.bz2 root:/sources# cd glibc-2.3.4 root:/sources/glibc-2.3.4# patch -Np1 -i./glibc-2.3.4-fixtest-1.patch. G: /dev/fd/63: No such file or directory g: warning: `-x c' after last input file has no effect g: no input files g: /dev/fd/63: No such file or directory g: warning: `-x c' after last input file has no effect g: no input files g: /dev/fd/63: No such file or directory g: warning: `-x c' after last input file has no effect g: no input files make1:.
/sources/glibc-build/c-types-check.out Error 1 make1: Leaving directory `/sources/glibc-2.3.4' make:. check Error 2Warning popup as before. Referring to the Notes. Code: root:/sources/glibc-build# make check. Mv -f /sources/glibc-build/tls.makeT /sources/glibc-build/tls.make make1: Leaving directory `/sources/glibc-2.3.4' make1: Entering directory `/sources/glibc-2.3.4' make -C csu tests make2: Entering directory `/sources/glibc-2.3.4/csu' make2:. No rule to make target `/sources/glibc-build/csu/tst-empty.out', needed by `tests'.
Make2: Leaving directory `/sources/glibc-2.3.4/csu' make1:. csu/tests Error 2 make1: Leaving directory `/sources/glibc-2.3.4' make:. check Error 2Stopped here. Code: mount: mount point /dev/pts does not exist Whenever you reenter chroot (after rebooting) while you're doing chapter 6, you need to also re-do the second section under 'populating /dev': section 6.8.2. You need to mount a tmpfs on /dev, then run mknod a few times, then create some symlinks, then create two directories (/dev/pts and /dev/shm), and only then should you do the mount commands that you did here. The reason for this is that /dev is a tmpfs (an in-memory filesystem), which means it gets cleared after every reboot. Amex optima/oasis program.
If you don't do 6.8.2 on every reboot, you need to do a few more things to clean out /dev before doing it - I'll go through those steps later. G: /dev/fd/63: No such file or directory This is an error, and it's happening because section 6.8.2 didn't happen on this boot. One of the symlinks that gets created is /dev/fd, which g apparently requires. What you need to do: 1) Remove everything in /mnt/lfs/dev (either from Konqueror, or from the shell, whatever you want). 2) Go through 6.8.1 and 6.8.2 again. I'm saying to remove everything, then do 6.8.1, because if you don't have the tmpfs mounted on /dev, then any writes to /dev/zero (for example) will create a new file there, instead of writing to the existing device. So you need to delete those files.
It's easiest to just delete everything in /dev (/mnt/lfs/dev, from the Fedora host), then do section 6.8.1 (creating /dev/console and /dev/null) again. Then, you can do 6.8.2 and re-try building glibc. Last edited by bwkaz; at 07:40 PM. Code: total 4 drwxrwxrwt 4 root root 320 Jul 29 11:59. Drwxr-xr-x 21 root root 4096 Jul 27 17:15.
Ysdeps/i386/i686 -Isysdeps/i386/i486 -Inptl/sysdeps/i386/i486 -Isysdeps/i386/fpu -Isysdeps/i386 -Isysdeps/wordsize-32 -Isysdeps/ieee754/ldbl-96 -Isysdeps/ieee754/dbl-64 -Isysdeps/ieee754/flt-32 -Isysdeps/ieee754 -Isysdeps/generic/elf -Isysdeps/generic -DLIBCREENTRANT -DLIBCREENTRANT -include include/libc-symbols.h /sources/glibc-build/c-types-check.out make1: Leaving directory `/sources/glibc-2.3.4'No error indicated here. Root:/sources/glibc-build# touch /etc/ld.so.conf root:/sources/glibc-build# make install. /sources/glibc-build/elf/ldconfig /lib /usr/lib CC='gcc' /usr/bin/perl scripts/test-installation.pl /sources/glibc-build/ Your new glibc installation seems to be ok.
Code: /mnt/lfs/sources/linuxthreads/man /mnt/lfs/sources/coreutils-5.2.1/man /mnt/lfs/sources/diffutils-2.8.1/man /mnt/lfs/sources/gettext-0.14.3/gettext-runtime/man /mnt/lfs/sources/gettext-0.14.3/gettext-tools/man /mnt/lfs/sources/ncurses-5.4/doc/html/man /mnt/lfs/sources/ncurses-5.4/man /mnt/lfs/tools/man /mnt/lfs/tools/share/man /mnt/lfs/usr/local/share/man /mnt/lfs/usr/local/man /mnt/lfs/usr/share/man /mnt/lfs/usr/man /mnt/lfs/opt/manman is on /mnt/lfs/sources/linuxthreads/man I stopped here. Please advise whether to change the path or otherwise. After this deadknot do I need to repeat this section - 6.11. Glibc-2.3.4 OR just starting from # make -C./glibc-2.3.4/linuxthreads/man B.R. Code: make: Entering directory `/sources/glibc-2.3.4/linuxthreads/man' install.3thr /usr/man/man3.
Remember to run /usr/sbin/makewhatis /usr/man at some point make: Leaving directory `/sources/glibc-2.3.4/linuxthreads/man'Re:- ' '. Remember to run /usr/sbin/makewhatis /usr/man at some point' Whether I have to run 'usr/sbin/makewhatis' and '/usr/man' (these 2 commands) at the end of this Section??? OR at any place thereafter??? Configuring Glibe All went through without problem. Moved on to following sections.
I got problem running this script $ sh mac -dev (ignored.) mac: line 110: /usr/local/bin/virtualenvwrapper.sh: No such file or directory The installation of virtualenvwrapper was removed in. It seems that pip install virtualenvwrapper is still required. Driver windows 7 ultimate. Should we add it back? BTW, my environment is even worse. The built-in python 2.7.10 on MacOS is not with pip. I need sudo easyinstall pip it. So here is what works for me: sudo easyinstall -upgrade pip sudo pip install virtualenvwrapper source '$HOMEBREWPREFIX/bin/virtualenvwrapper.sh' If it's okay, I'd make the PR.
On Tue, Aug 29, 2017, 13:01 Achi Chen.@. wrote:, I got problem running this script $ sh mac -dev (ignored.) mac: line 110: /usr/local/bin/virtualenvwrapper.sh: No such file or directory The installation of virtualenvwrapper was removed in #diff-140c1f12feeb2c52dfbeb2da6066a73a. It seems that pip install virtualenvwrapper is still required. Should we add it back? BTW, my environment is even worse. The built-in python 2.7.10 on MacOS is not with pip.
Sqlstate Hy000 2002 No Such File Or Directory
I need sudo easyinstall pip it. So here is what works for me: sudo easyinstall -upgrade pip sudo pip install virtualenvwrapper source '$HOMEBREWPREFIX/bin/virtualenvwrapper.sh' If it's okay, I'd make the PR. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
On Tue, Aug 29, 2017, 13:01 Achi Chen.@. wrote:, I got problem running this script $ sh mac -dev (ignored.) mac: line 110: /usr/local/bin/virtualenvwrapper.sh: No such file or directory The installation of virtualenvwrapper was removed in #diff-140c1f12feeb2c52dfbeb2da6066a73a. It seems that pip install virtualenvwrapper is still required. Should we add it back? BTW, my environment is even worse. The built-in python 2.7.10 on MacOS is not with pip. I need sudo easyinstall pip it.
So here is what works for me: sudo easyinstall -upgrade pip sudo pip install virtualenvwrapper source '$HOMEBREWPREFIX/bin/virtualenvwrapper.sh' If it's okay, I'd make the PR. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.