Daniel Carrera writes: > > I'm working on install instructions for Linux: > > https://sourceforge.net/apps/mediawiki/pdl/index.php?title=Installing_PDL_on_Linux > > I'm taking the approach of actually *testing* > the install on a *pristine* copy of each OS. > I document the results, and I list other > distributions for which the results should > probably apply. It takes longer to do it this way, > but you get more dependable install instructions.
Great! > I would like to have a list of *key* modules that > I should try to get working. I don't want to test > every possible module. I want to test a small set > of key modules. This is what I have so far: > > * PGPLOT > * PLplot > * Graphics::TriD You are talking binary installs, yes? I would suggest extracting a copy of the PDL source for the version installed and just run the desired test programs in PDL/t/. If you are talking about manual build installs, I suggest trying a clean PDL, clean OS run first keeping logs of the process. I use this for my runs: ( set -x ; perl Makefile.PL ; make ; make test ) 2>&1 | tee -a ../pdl-246015-vanilla-log.txt Then you can do 'perl -Mblib t/opengl.t' or whatever your desired test. NOTE: I believe a PDL build with all the WITH_* options for external dependencies turned off should build as long as the OS has C and perl development environments. > Does that look like a good list? Anything I > missed? If you suggest another module, please also > suggest how I can get it working and a simple test > to confirm that it is working. Thanks. Look at PDL/cygwin/INSTALL has some (now out-of-date) notes from the cygwin build testing. Cheers, Chris
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
