No luck. After splitting up the link file into 6, the compilation of the first file actually proceeded. I saw lapack_link_100 being processed in the build directory.
Immediately after that, instead of starting compilation of #101, I got the following output: ------------------ No source code in DATA section for Inline 'Pdlpp' section. at lapack_test.pl line 0 INIT failed--call queue aborted. One or more DATA sections were not processed by Inline. ---------------------- New link file: # file that links all lapack link files together use lapack_link_100; use lapack_link_101; use lapack_link_102; use lapack_link_103; use lapack_link_104; use lapack_link_105; #Scanned files: 425, with errors in parsing : 93, OK: 332 1; Chris Marshall wrote: > Jan Hoogenraad wrote: >> Thanks a lot for the feedback. >> I've included your comments in the test code. >> >> The new test program can be found in lapack_090602.tgz, under >> https://sourceforge.net/tracker/?func=detail&atid=350612&aid=2774886&group_id=612 >> >> >> >> Can you help me out on the how to reduce the huge memory hunger (>> 2Gb >> swap space needed, then I have terminated the process) for compilation ? >> The intermediate C file grows to 43 Mb >> 42644492 lapack_link_pm_e10d.c > > Split the interface across multiple XS files. > For example, the PDL/Lib/GSL splits the interfaced > routines across a number of folders... > > --Chris > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
