On 14/04/2012 14:58, Kai Tietz wrote:
> 2012/4/14 Nicolai Josuttis:
>> The first problem was that
>> build/gcc/gengtype-lex.c
>> was created with DOS-Newlines (CR-LF),
>> which makes the following compiling fail:
>> make[2]: Entering directory `/cygdrive/p/gcc480snap-install/build/gcc'
>> gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual
>> -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute
>> -Wold-style-definition -fno-common -Wno-error -DHAVE_CONFIG_H
>> -DGENERATOR_FILE -I. -Ibuild -I../../src/gcc-4.8-20120401/gcc
>> -I../../src/gcc-4.8-20120401/gcc/build
>> -I../../src/gcc-4.8-20120401/gcc/../include
>> -I../../src/gcc-4.8-20120401/gcc/../libcpp/include
>> -I/cygdrive/p/gcc480snap-install/build/./gmp
>> -I/cygdrive/p/gcc480snap-install/src/gcc-4.8-20120401/gmp
>> -I/cygdrive/p/gcc480snap-install/build/./mpfr
>> -I/cygdrive/p/gcc480snap-install/src/gcc-4.8-20120401/mpfr
>> -I/cygdrive/p/gcc480snap-install/src/gcc-4.8-20120401/mpc/src
>> -I../../src/gcc-4.8-20120401/gcc/../libdecnumber
>> -I../../src/gcc-4.8-20120401/gcc/../libdecnumber/bid -I../libdecnumber \
>> -o build/gengtype-lex.o gengtype-lex.c
>> After SED-ing CR-LF to LF in that file the compilation continues.
> About this SED issue I am not sure if this is for real a gcc bug.
When this happens, it's usually a result of using a Windows GUI program to
unpack the tarball rather than the command-line tar program. WinZIP in
particular has a "helpful" option setting somewhere in the prefs that
automatically converts LF-ending files to CR-LF on unpack, IIRC. Use "tar
-xvfj gcc-4.8-20120401.tar.bz2" instead.
cheers,
DaveK
