Hi, On Sun, Oct 20, 2002 at 01:32:41PM +0100, Major A wrote: > I guess your times are "user" CPU times? Mine are, at least.
Sorry for not mentioning, I used the "real" time. > > Linux i386 2.4.19 (Debian Woody, Athlon 1.4 GHz, 512 MB) > > Compilation time: 2m3.280s > > Same with gcc 2.95.4: 1m52.649s (anyone under one minute? :-) > > gcc 2.95.4 from Debian sid, Athlon XP1800+ (1.53), 256MB: 1m34s. Is it > the PC2700 CL2 memory that makes the difference? The above mentioned (real) times are from an Athlon XP1600+ (1.4 GHz real frequency). I'm not sure, which RAM is used. It's remote, so I can't just open it. Here is the complete time output: real 1m52.472s user 1m38.540s sys 0m13.400s So it's probably just the processor frequency. > gcc 2.95.2 from Debian potato, 2x Alpha ev67 667, 1GB: 2m21s. > > On the same machine, DEC's own CC says > > ccc -o scanimage scanimage.o stiff.o ../backend/.libs/libsane.a -ldl > ../lib/liblib.a -lnsl -lm -ljpeg > /usr/lib/compaq/ccc-6.2.9.002-2/alpha-linux/bin/ld: scanimage: Not enough > room for program headers (allocated 6, need 7) > /usr/lib/compaq/ccc-6.2.9.002-2/alpha-linux/bin/ld: final link failed: Bad > value > make[1]: *** [scanimage] Error 1 > > Not good, not sure what we can do about it. This error occurs after > 47s though, so we have a candidate... What does the linker mean by "program header"? Bye, Henning
