Re: still can't compile term-readkey-pm5184 == it creates ReadKey.Bundle but then "no suitable image found" in ReadKey.bundle

Tom Liehe via Fink-beginners <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Message-ID <[email protected]>
So I looked at issue 461 and see that neider wrote:

For the record, I forced perl5184 on 10.15, symlinked perl5.18->perl5.18.4, and built term-readkey-pm5184 without any problems.

But I don’t know how to do this although it sounds simple.
1) How did he “force” perl5184?
2) where was the symlink performed?

Thanks, Hanspeter, for your help. Hope you can give a non-programmer some easy commands.

Tom

> On Nov 21, 2019, at 5:50 AM, Hanspeter Niederstrasser <[email protected]> wrote:
> 
> On 11/19/19 3:24 PM, Tom Liehe via Fink-beginners wrote:
>> 
>> Can't load 'blib/arch/auto/Term/ReadKey/ReadKey.bundle' for module Term::ReadKey: dlopen(blib/arch/auto/Term/ReadKey/ReadKey.bundle, 1): no suitable image found.  Did find:
>> 	file system relative paths not allowed in hardened programs at /System/Library/Perl/5.18/darwin-thread-multi-2level/DynaLoader.pm line 194.
>>  at /System/Library/Perl/5.18/darwin-thread-multi-2level/DynaLoader.pm line 98.
>> 	DynaLoader::croak('Can\'t load \'blib/arch/auto/Term/ReadKey/ReadKey.bundle\' fo...') called at /System/Library/Perl/5.18/darwin-thread-multi-2level/DynaLoader.pm line 194
>> 	DynaLoader::bootstrap('Term::ReadKey') called at ReadKey_pm.PL line 515
>> Creating ReadKey.pm
>> Bootstrapping the XS for blockoptions: make: *** [ReadKey.pm] Error 255
> 
> This is https://github.com/fink/fink-distributions/issues/461 <https://github.com/fink/fink-distributions/issues/461>
> 
> Hanspeter

_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.