Re: [Devil-linux-develop] more boot features

[<hzu...@ra...>]

On 04/29/2004 09:46:33 AM Bruce Smith wrote:
>> >I've been looking at adding "mon" on the feature requests.
>> >
>> >My research shows it needs a bunch of perl modules we don't have,
>> >and I've never added a perl module to DL.  Is anything required
>> >other than uploading the source of the module to the perl-ext
>> >subdirectory?
>>
>> Sometimes you have to patch the Makefile.PL to get rid of the prompts.
>>
>> Just copy the stuff into the perl-ext directory and recompile perl.
>> If it prompts for something, then you know you have to patch it. ;-)
>
>Maybe I won't add "mon" ...
>Any clue what to do about this?
>
>
>Making IO-Tty-1.02 (nonxs)
>Can't load module IO, dynamic loading not available in this perl.
>(You may need to build a new perl executable which either supports
>dynamic loading or has the IO module statically linked into it.)
>at ../../lib/IO/Handle.pm line 260
>Compilation failed in require at ../../lib/IO/Handle.pm line 260.
>BEGIN failed--compilation aborted at ../../lib/IO/Handle.pm line 260.
>Compilation failed in require at ../../lib/IO/Seekable.pm line 101.
>BEGIN failed--compilation aborted at ../../lib/IO/Seekable.pm line 101.
>Compilation failed in require at ../../lib/IO/File.pm line 117.
>BEGIN failed--compilation aborted at ../../lib/IO/File.pm line 117.
>Compilation failed in require at Makefile.PL line 5.
>BEGIN failed--compilation aborted at Makefile.PL line 5.
>Warning: No Makefile!
>make[1]: Entering directory `/data/build/tmp/perl-5.8.3/ext/IO-Tty-1.02'
>make[1]: *** No rule to make target `config'.  Stop.
>make[1]: Leaving directory `/data/build/tmp/perl-5.8.3/ext/IO-Tty-1.02'
>make config failed, continuing anyway...
>make[1]: Entering directory `/data/build/tmp/perl-5.8.3/ext/IO-Tty-1.02'
>make[1]: *** No rule to make target `all'.  Stop.
>make[1]: Leaving directory `/data/build/tmp/perl-5.8.3/ext/IO-Tty-1.02'
>make: *** [ext/IO-Tty-1.02/pm_to_blib] Error 2
>ERROR
>/data/build/scripts/perl build failed
>check log file /data/build/tmp/LOGS/build/perl for details

That problem I saw on other perl-ext packages too, but never found out
where it comes from.

Do we have any perl experts here ?

Heiko