Front page | perl.perl5.porters |
Postings from December 2004
On Mon, Dec 27, 2004 at 09:45:19PM +0000, Bennett Todd wrote: > So anyway, naturally the next thing is to start building perl with > favourite xs-requiring modeles linked in. From the docs I'd have > thought that just unpacking under ext/ would have sufficed, but it > uniformly and resoundingly doesn't; they end up in nonxs_ext, and > when run whinge because dynamic loading isn't available. > > Gotta rename the dir the tarballs extract to something resembling > the install path. E.g., after extracting Text-CSV_XS-0.23.tar.gz in > ext/, you need to mkdir Text; mv Text-CSV_XS-0.23 Text/CSV_XS. > > That seems to suffice. This may seem like a kludge, but I believe that the intended way of making perl with statically linked extensions is as follows: 0: Build and install perl from the distribution tarball for each extension 1: Unpack it 2: Run perl Makefile.PL it should 3: Realise that you have a static perl and figure things out appropriately 4: make all test (which should make the targets "static" and "aperl" along the way) 5: make install which installs a new perl binary with all the old extensions plus this one linked in. To do this, perl and each extension should be installing .a files in the siteperl tree, so that each subsequent extension can re-link against the core perl code and all the previous extensions. Nicholas ClarkThread Previous | Thread Next