P Kishor wrote: > ah! Now I get it. Well, that is rather sad. I checked PDL::IO::HDF5, > and it doesn't seem ready for primetime, in that, it doesn't support > all of HDF5 functionality. One of the reasons I was inspired to do all > these shenanigans was because yesterday I attended a "Python Bootcamp" > here on UW-Madison campus, and went through sessions on Numpy, Scipy > and PyTables. The latter, especially in conjunction with ViTables (a > graphical browser of HDF5 data) was really impressive, and I thought, > "I can do dat wit my PDL." But then... > well, usually functionality doesn't get added to PDL until someone needs it. And usually the person who needs it is the one to add it, for the benefit of all. Contributions are always welcome! > >> that moves the Makefile to Makefile.old (as you see in your output below), >> so it's not surprising that the next "make" doesn't do anything. My advice: >> go to the top-level, do a "make realclean", then "perl Makefile.PL" and >> start over. Inspect the output of that command carefully to see if there >> are any dire warnings. >> >> > > ok. So, are you saying that I do a 'make realclean' and 'perl > Makefile.PL' for the entire PDL, or for just FITS? the whole thing. > Doing so for the > latter results in > > punk...@lucknow ~/Projects/PDL-2.4.6/IO/FITS$make > cp FITS.pm blib/lib/PDL/IO/FITS.pm > Manifying blib/man3/PDL::IO::FITS.3 > punk...@lucknow ~/Projects/PDL-2.4.6/IO/FITS$ > > > >> I could see you getting in this situation if you did the Makefile.PL, then >> realized you needed some other modules (Astro::FITS::Header maybe?), and >> then ran make without redoing the Makefile.PL. >> >> Derek >>
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
