develooper Front page | perl.perl5.porters | Postings from October 2003

Re: 5.8.1: static build completely busted?

Thread Previous | Thread Next
Andy Dougherty
October 10, 2003 06:22
Re: 5.8.1: static build completely busted?
Message ID:
On Thu, 9 Oct 2003, Ilya Zakharevich wrote:

> On Thu, Oct 09, 2003 at 04:46:18PM -0400, Andy Dougherty wrote:
> > There is only one missing '.a' file:  lib/auto/B/C.a isn't linked in for
> > some reason.
> See my initial message for the reason.

Oh, I understood it at that level.  What I was wondering was why the 'B'
extension Makefile.PL wasn't written to include the B::C module
automatically as I had expected it would.

> Just change two lines I marked in Makefile, and one can remove these
> special cases from Configure.

> > I don't see any immediate problem with this, since the lists generated in
> > my case are identical (except for B/C.a).  However, what about after perl
> > is installed and you want to build a new perl?  Where will MakeMaker get
> > the approrpriate list of libraries?
> Makemaker builds this list itself: the *.a files are installed,
> makemaker scans for them, and builds the list of things to link.  This
> is why my recipe in "b" works (one which uses `make perl' in a
> subdirectory via MakeMaker).

Ah, good.  Then it sounds like your basic plan will work.  It's probably
worth trying it in bleadperl, as long as someone's game to keep an eye out
in case there are unanticipated consequences.

I thought about it carefully, but would it make sense to use miniperl to
generate the */*/*.a list instead of the shell?

Thanks for the careful research and testing,

    Andy Dougherty

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About