sci-chemistry/raster3d-2.7s: fails to compile with gfortran 4.1.2. If you try: emerge =sci-chemistry/raster3d-2.7s it fails with a gfortran error Reproducible: Always Steps to Reproduce: 1.emerge sci-chemistry/raster3d-2.7s 2. 3. Actual Results: >>> Emerging (1 of 2) sci-chemistry/raster3d-2.7s to / * Raster3D_2.7s.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking Raster3D_2.7s.tar.gz ;-) ... [ ok ] * You need one of these Fortran Compilers: gfortran g77 * Installed are: gfortran >>> Unpacking source... >>> Unpacking Raster3D_2.7s.tar.gz to /var/tmp/portage/sci-chemistry/raster3d-2.7s/work * Applying patches for selected FORTRAN compiler: gfortran >>> Source unpacked. >>> Compiling source in /var/tmp/portage/sci-chemistry/raster3d-2.7s/work/Raster3D_2.7s ... mv render.f render.f.bak egrep -v '(CARRIAGECONTROL|DISPOSE)' render.f.bak > render.f mv normal3d.f normal3d.f.bak egrep -v '(CARRIAGECONTROL|DISPOSE)' normal3d.f.bak > normal3d.f mv rastep.f rastep.f.bak egrep -v '(CARRIAGECONTROL|DISPOSE)' rastep.f.bak > rastep.f Making Raster3D 2.7s for linux x86_64-pc-linux-gnu-gcc -g -w -I/usr/include -I/usr/local/include -DGUNZIP -DIMAGEPIPE -DTIFF_SUPPORT -DTIFF_INVERT -DJPEG_SUPPORT -DPNG_SUPPORT -DLINUX -DNETWORKBYTEORDER -Wl,-O1 -o avs2ps avs2ps.c -lm gfortran -fno-range-check -w -o balls balls.f gfortran -fno-range-check -w -c -o quadric.o quadric.f gfortran -fno-range-check -w -c -o suv.o suv.f gfortran -fno-range-check -w \ rastep.f quadric.o suv.o -Wl,-O1 \ -o rastep gfortran -fno-range-check -w -c -o render.o render.f In file render.f:3696 CALL ASSERT(TYPE(INEXT).EQ.VERTRANSP,'lost vertex transp' 1 Error: Syntax error in argument list at (1) make: ** [render.o] Erro 1 Expected Results: emerge succefuly The problem is ***FIXED*** if you run: FFLAGS+="-ffixed-line-length-none" emerge sci-chemistry/raster3d-2.7s
Thank you very much for pointing this out. There are definitely a few source files with lines longer then 72 characters in the tarball. Strangely, gcc-4.3 doesn't seem to have a problem with them. In any case, I've changed the ebuild to append -ffixed-line-length-132 (the extended source length) to the FFLAGS which should take care of this. Best, Markus
