Gcc Error Writing To Broken Pipe
Sign in Pricing Blog Support Search GitHub This repository Watch 20 Star 329 Fork 108 lericson/pylibmc Code Issues 24 Pull requests 2 Projects 0 Wiki Pulse Graphs New issue Compile fails: "fatal error: error writing to -: Broken pipe" #35 Closed rays opened this Issue Mar 29, 2011 · 4 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 4 participants rays commented Mar 29, 2011 I'm using xcode4 and trying to compile pylibmc on a new machine running osx 10.6.7 and get the following error running install running build running build_py running build_ext building '_pylibmc' extension creating build/temp.macosx-10.6-universal-2.6 gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch ppc -arch x86_64 -pipe -DUSE_ZLIB -I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c _pylibmcmodule.c -o build/temp.macosx-10.6-universal-2.6/_pylibmcmodule.o /usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler (/usr/bin/../libexec/gcc/darwin/ppc/as or /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed Installed assemblers are: /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64 /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386 _pylibmcmodule.c:2028: fatal error: error writing to -: Broken pipe compilation terminated. lipo: can't open input file: /var/folders/8q/8q7FGaB3FHq8zCFUe4wSVk+++TI/-Tmp-//ccfKEKaS.out (No such file or directory) error: command 'gcc-4.2' failed with exit status 1 rays commented Mar 30, 2011 Turns out PPC libraries are no longer in xcode 4, but ARCHFLAGS is supported and you can tell gcc not to use ppc, whew export ARCHFLAGS='-arch i386 -arch x86_64' rays closed this Mar 30, 2011 jbergstroem commented Mar 30, 2011 Could/should be in docs, helpful comment Owner lericson commented Mar 30, 2011 Major WTF at Apple's QA... Want to know why this happens? Apple's new Xcode release removes the assembler for PPC, while the core system retains their PPC images in the fat binaries. If you were to run file /usr/bin/python you would most likely find the following: /usr/bin/python: Mach-O universal binary with 3 architectures /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/bin/python (for architecture i386): Mach-O executable i386 /usr/bin/python (for architecture ppc7400): Mach-O executable ppc Python compiles C extensions with the same compiler flags
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community https://github.com/lericson/pylibmc/issues/35 Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Broken Pipe error when using pip to install pycrypto on Mac OS X up vote 29 down vote favorite 13 I am attempting to install pycrypto (version http://stackoverflow.com/questions/5944332/broken-pipe-error-when-using-pip-to-install-pycrypto-on-mac-os-x 2.3) on OS X via pip. I am getting a "Broken pipe" error when the compiler attempts to compile MD2.c. I get a very similar error when using easy_install. Here is the error that I am getting: bash-3.2$ bash-3.2$ sudo pip install pycrypto Password: Downloading/unpacking pycrypto Running setup.py egg_info for package pycrypto Installing collected packages: pycrypto Running setup.py install for pycrypto warning: GMP library not found; Not building Crypto.PublicKey._fastmath. building 'Crypto.Hash.MD2' extension gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -fwrapv -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch ppc -arch x86_64 -pipe -std=c99 -O3 -fomit-frame-pointer -Isrc/ -I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c src/MD2.c -o build/temp.macosx-10.6-universal-2.6/src/MD2.o /usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler (/usr/bin/../libexec/gcc/darwin/ppc/as or /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed Installed assemblers are: /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64 /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386 src/MD2.c:134: fatal error: error writing to -: Broken pipe compilation terminated. lipo: can't open input file: /var/tmp//cc47qHNI.out (No such file or directory) error: command 'gcc-4.2' failed with exit status 1 Complete output from command
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://superuser.com/questions/554855/how-can-i-fix-a-broken-pipe-error developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's https://groups.google.com/d/topic/harbour-users/Ow2_bKRfpLc how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How can I fix a Broken Pipe error? up vote 17 down vote favorite 5 I recently gcc error reinstalled RVM (following the instructions at http://rvm.io) after a fresh install of Ubuntu 12.10 when I got an SSD Drive. Now, when I type: type rvm | head -1 I receive the following error: rvm is a function -bash: type: write error: Broken pipe But if I immediately repeat the command then I only receive: rvm is a function And it appears everything is ok? What's happening? What can I do to fix it? It doesn't happen always. It appears gcc error writing to be more sporadic. I've tried to find some kind of pattern to it but haven't yet. bash ruby .bash-profile rvm share|improve this question edited Feb 20 '13 at 16:44 terdon 33.5k66299 asked Feb 20 '13 at 15:29 Jason Shultz 2352410 add a comment| 3 Answers 3 active oldest votes up vote 27 down vote accepted Seeing "Broken pipe" in this situation is rare, but normal. When you run type rvm | head -1, bash executes type rvm in one process, head -1 in another.1 The stdout of type is connected to the "write" end of a pipe, the stdin of head to the "read" end. Both processes run at the same time. The head -1 process reads data from stdin (usually in chunks of 8 kB), prints out a single line (according to the -1 option), and exits, causing the "read" end of the pipe to be closed. Since the rvm function is quite long (around 11 kB after being parsed and reconstructed by bash), this means that head exits while type still has a few kB of data to write out. At this point, since type is trying to write to a pipe whose other end has been closed – a broken pipe – the write() function it caled will return an EPIPE error, translated as "Broken pipe". In addition to this error, the kernel also sends the SIGPIPE signal to type, which by default k
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen