Greetings all, As you know in the past we have made rather stern warnings about what version of gcc you should use for compiling SVDPACKC. However, I found myself working these days with version 4.1.1 of gcc, and having absolutely no problems with SVDPACKC (the problem in the past has been rather inexplicable segementation faults when running las2).
So....I might temper our version requirements a bit in light of my experience of late - in the past we have suggested using a 3.2 or 3.3 version of gcc, but I'm not sure if that's either realistic or necessary at this point. If you've had any experiences with SVDPACKC good or bad that might shed some light on this, I'd be happy to hear about them. I am actually not a high powered user of gcc, so I'm wondering if there might not be some option settings I don't know about that might help resolve some of this inconsistency as we move from version to version of gcc. Right now we just compile like this... gcc -ansi -O -c las2.c Also, I found that I was having a hard time compiling SVDLIBC on a Xeon processor - so my efforts on that front are momentarily stalled, but will surely continue. So, I'll be updating CPAN with a new development release of SenseClusters sometime in the next few days that will hopefully resolve some issues with svdpackout.pl and might have better guidelines about compiling SVDPACKC. Thereafter we'll move on to considering the issue of SVDPACKC versus SVDLIBC. Cordially, Ted -- Ted Pedersen http://www.d.umn.edu/~tpederse ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ senseclusters-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/senseclusters-users
