grep: write error: Broken pipe
Hi, all. I'm new to FreeBSD and have a newbie question (or maybe a couple). I was running FreeBSD 8.2-RC3 and recently `freebsd-update'd to 8.2-RELEASE. Now when I build or upgrade ports I get lots of these grep: write error: Broken pipe messages during builds. This is more of a nuisance than anything else, but last night when trying to build the GIMP from Ports, the build failed while trying to build the prerequisite OpenEXR 1.6.1_3 (output appended below). I can't figure out why the build fails for OpenEXR; as far as I can tell all the dependencies (in particular IlmBase in /usr/local/lib) are in place. I know the two are probably not related, but can anyone speculate as to the cause of these grep: write error: Broken pipe messages and where I might try looking to fix it? I'm hoping the answer will indirectly lead to some clues that will help me debug my failed OpenEXR build. (I'm asking here because I didn't want to bug the maintainer with what is probably a stupid newbie question.) My other question is, those of you who answer questions and debug problems on this list, what do you all get out of it? I feel kind of selfish asking for what is basically free technical support; how best can I repay you all? All the best, Austin OUTPUT OF make install FOR OpenEXR-1.6.1_3 root@freebsd:/usr/ports/graphics/OpenEXR# make install === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for OpenEXR-1.6.1_3 = SHA256 Checksum OK for openexr-1.6.1.tar.gz. === Patching for OpenEXR-1.6.1_3 === Applying FreeBSD patches for OpenEXR-1.6.1_3 === OpenEXR-1.6.1_3 depends on executable: gmake - found === OpenEXR-1.6.1_3 depends on package: libtool=2.4 - found === OpenEXR-1.6.1_3 depends on executable: pkg-config - found === OpenEXR-1.6.1_3 depends on shared library: Half.6grep: write error: Broken pipe - found === Configuring for OpenEXR-1.6.1_3 checking build system type... i386-portbld-freebsd8.2 checking host system type... i386-portbld-freebsd8.2 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether gmake sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for style of include used by gmake... GNU checking dependency style of c++... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gcc... cc checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking dependency style of cc... gcc3 checking whether ln -s works... yes checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... cpp checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... c++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for epcf90... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for gfortran... gfortran checking whether we are using the GNU Fortran 77 compiler... yes checking whether gfortran accepts -g... yes checking the maximum length of command line arguments... (cached) 262144 checking command to parse /usr/bin/nm -B output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if cc static flag works... yes checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC
Re: grep: write error: Broken pipe
?? avs...@mail.ru wrote: ... how best can I repay you all? IMO, by paying it forward: as you become more familiar with/ knowledgeable of FreeBSD, continue to read freebsd-questions@ and assist when able. Everyone here was new to Unix and/or to FreeBSD at one time. Some of us still are :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: grep: write error: Broken pipe
On Sun, 6 Mar 2011, ?? ??? wrote: My other question is, those of you who answer questions and debug problems on this list, what do you all get out of it? I feel kind of selfish asking for what is basically free technical support; how best can I repay you all? When you become knowledgeable, start answering questions yourself. I rarely have anything to contribute, but when I do I'll answer a question. As to why, there's an element of long-term self-interest: the more successes there are, the larger the user base becomes, the more experts develop. As a FreeBSD user, it's in my interest to have a large installed base and a large and robust user community since this will (I think and hope) ultimately mean more awareness from hardware makers and thus a continued supply of hardware I can use. Well, applications software too. And if you become an expert, maybe you can answer *my* question next time :^) -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
