> > Here is the summary of questions I would like to have answers : > > 1. What's the advantage of Makefile.PL files? Could you have written > only a simple Makefile?
Makefile.PL is the standard Perl way to generate a OS specify Makefile. (Most non Perl application use configure for that purpose, basicly both do the same). > 2. What is the use of all the .c files (generated by Makefile) under > /xs subdirectories (/App, /Component, /Syntax, etc) They are the interface between the C Part of Embperl and the Perl > 3. Why I have to manually build the .c files in these subdirectories > before building from CPAN and I am not required to do so if I compile > Embperl myself? That's because a module (ExtUtils::MakeMaker) that Makefile.PL uses to generate the Makefile, has changed in recent version of Perl and has changed the order in which things are compiled. On most system the files in the xs subdirectory get compiled first and everthing is fine, but on BSD and AIX the file in the root directory get compiled first, which fails, because they depends on files in the xs directory. I have fixed this, but because of the change in MakeMaker I have to create a new fix for Perl 5.8.x. > 4. Why did I have to copy the top-level header files (ep.h, > epmacro.h, etc) in these subdirectories for CPAN to compile correctly > and I were not required to do so when compiling Embperl myself? Normaly you shouldn't need to do this.There seems some problem with include paths on AIX. > 5. Could I had fixed the missing header files by making CPAN look in > the top-level directory? How? There will be a way to fix this, but I don't know how yet. > 6. What are .exp files. Why does Embperl need to be linked with .exp > files found under /Apache2/, what is the big deal behind .exp files? Most Unix store the information about functions that are availabe inside a library file in the file itself, on AIX they are stre in the exp files. The linker needs the exp files to find the correct entry point for functions inside a library. > > > You might want to answer "Look, it works if you build Embperl > yourself, why bother with CPAN?" > CPAN, basicly does the same as you should do manualy. The extra steps you need to do are only AIX specific problems and I hope we can sort them out and fix it. > I just want to UNDERSTAND in what CPAN builds the software > differently. As far as I know, It would use the SAME top-level > Makefile to build Embperl; I don't understand why building from CPAN > forces me to compile /xs subdirectories by and and gives me missing > headers errors, and running the Makefile manually don't return me > these errors. > > Well, if I have answer to these 6 main questions, I will feel better > and maybe sleep better tonight :-) > I hope my answer make a little sense to you Gerald > I will test Embperl against Apache2/mod_perl2 on this Aix box later > today. Will keep you posted. > > Thank you VERY MUCH for your great support and for taking time to > answer my questions. It is very appreciated. > > Best regards, > > Steve Hemond > Programmeur Analyste / Analyst Programmer > Smurfit-Stone, Ressources Forestières > La Tuque, P.Q. > Tel.: (819) 676-8100 X2833 > [EMAIL PROTECTED] -------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh IT-Securitylösungen * dynamische Webapplikationen * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 939-122 WWW: http://www.ecos.de/ Fax: +49 6133 939-333 -------------------------------------------------------------- | | ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info | +------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
