------- Additional Comments From vincent dot riviere at freesbee dot fr 2007-05-30 21:41 ------- My previous solution is not so good, because the main configure is run without the option igncr. And configure.in contains the line : baseargs=`cat conftestsed.out` Thus the generated Makefile contains unexpected CRs, which can be easyly seen by using less : BUILD_CONFIGARGS = --cache-file=../config.cache --build=i686-pc-cygwin -- host=i686-pc-cygwin --target=i686-pc-cygwin ^M --program-transform- name='s,y,y,^M' --with-build-subdir="$(BUILD_SUBDIR)"
The real, whole solution is to not modify the sources of the binutils, and run the following commands for bulding the binutils : set -o igncr export SHELLOPTS # The child bashes will automatically do set -o igncr configure make This is the definite solution when using igncr. The binutils can't do anything against the bogus cat behaviour of Cygwin (except not using cat) I have written a lot of comments here (and I have learned a lot, too). Now, I go to back to the top and I look at the title of this bug 4334 : "MAKE FAILED: cpu-powerpc.o isn't added to libbfd.a ?" The real problem is that an innocent Cygwin user tries to build the binutils, and get an error message about an undefined reference, without any indication about what is really happening. We know that the problem is caused by cat on text filesystems, and there is at least 2 ways to bypass it : building from a binary filesystem, or using the igncr option. Any Cygwin user would be happy to use one of these solutions if it can help him to build the binutils ! So the binutils would be polite if it could detect if the `cat` problem is present, and tell the user how to bypass it. For example, a simple script like this in the main configure may be enough (or maybe wrapped into an autoconf macro) : echo a >file if test `cat file` != a then echo \`cat\` bug detected. echo Please run configure from on a binmode filesystem echo or use the igncr trick exit 1 fi Vincent -- http://sourceware.org/bugzilla/show_bug.cgi?id=4334 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
