Front page | perl.perl5.porters |
Postings from May 2008
On Thu, 29 May 2008, Steve Michel wrote:
> Hmmm.....one last tidbit & question, before I pursue alternate source...
>
> There were no errors or warnings during the configure step.
Config_heavy doesn't get built during the 'configure' step, but instead
during the build process. The commands (and the resulting output) should
look like this:
> > ./miniperl -Ilib configpm
> > written lib/Config.pod
> > updated lib/Config.pm
> > updated lib/Config_heavy.pl
You can always try rerunning 'configpm' manually just to be sure:
./miniperl -Ilib configpm
> There are no disk space issues
> nafiler6:/chucktestshare2_x 125829120 48594936 77234184 39%
> /plm/cinas/chucktestshare2
> Filesystem 1K blocks quota limit grace files
> quota limit grace
> /u/tdsmichl 562772 614400 614400 14207
> 40960 40960 Disk quotas for group nasdev (gid 667): none
> Disk quotas for group spider (gid 153): none
> Disk quotas for group techdev4 (gid 666): none
> Disk quotas for group noexport3 (gid 147): none
>
> Makefile, Config.pm and Config_heavy.pl are all built completely.
>
> -rw-r--r-- 1 tdsmichl pd 33852 May 29 12:46 Makefile
> -rw-r--r-- 1 tdsmichl pd 2874 May 29 13:06 lib/Config.pm
> -rw-r--r-- 1 tdsmichl pd 33750 May 29 13:06 lib/Config_heavy.pl
>
> /plm/cinas/chucktestshare2/perl.d/build_perl/macos> tail
> lib/Config_heavy.pl
> }
> }
>
> # Called by the real AUTOLOAD
> sub launcher {
> undef &AUTOLOAD;
> goto \&$Config::AUTOLOAD;
> }
>
> 1;
>
> But the end of the make step log complains about a missing Makefile ?
>
> touch uni.data
> sh writemain DynaLoader.o > perlmain.c
> `sh cflags "optimize='-O3'" perlmain.o` perlmain.c
>
> Making DynaLoader (static)
> *Warning: No Makefile!*
> make config failed, continuing anyway...
This is the same problem. The missing 'Makefile' is
ext/DynaLoader/Makefile. It is supposed to be built by
lib/ExtUtils/MakeMaker.pm, but MakeMaker failed at this point:
>> &Config::AUTOLOAD failed on Config::launcher at ../../lib/Config.pm
>> line 72.
The Config::launcher bit is the problem, and that's in Config_heavy.pl,
where it's supposed to be. I don't know what's going wrong here.
One other vague possibility that comes to mind is that there is some other
problem with your perl build (for example, perhaps Configure guessed wrong
about some of the functions that interact with the filesystem). One other
thing you can do is
make minitest
This will try to test out 'miniperl'. Some of the errors you see will be
irrelevant (they will come from being unable to open various as-yet
unbuilt modules). However, if you see anything suspicious, that might
point to the problem.
Sorry I don't have any better ideas at the moment,
--
Andy Dougherty doughera@lafayette.edu
Thread Previous
|
Thread Next