Bug 321877

Summary:	Commit 66c339d4216cc834014c38617c664647cf34d4b8 breaks build
Product:	[Unmaintained] bindings	Reporter:	Vadim Zhukov <persgray>
Component:	general	Assignee:	bindings-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	chrisburel
Priority:	NOR
Version First Reported In:	4.10
Target Milestone:	---
Platform:	OpenBSD
OS:	OpenBSD
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vadim Zhukov 2013-07-02 23:20:22 UTC

After commit 66c339d4216cc834014c38617c664647cf34d4b8 Perl modules are installed into

/usr/local/local/libdata/perl5/site-perl/...

instead of:

/usr/local/libdata/perl5/site-perl/...

Old value was detected correctly in 4.10.4. Please, revert the mentioned commit.

Reproducible: Always




Perl-related values in CMakeCache.txt are same in both cases. Here they are:

$ egrep '^([^/].*)?PERL' ../build-i386/CMakeCache.txt 
CUSTOM_PERL_SITE_ARCH_DIR:STRING=/usr/local/libdata/perl5/site_perl/i386-openbsd
PERL_EXECUTABLE:FILEPATH=/usr/bin/perl
PERL_INCLUDE_PATH:PATH=/usr/libdata/perl5/i386-openbsd/5.16.3/CORE
PERL_LIBRARY:FILEPATH=/usr/lib/libperl.so.13.0
PERL_EXECUTABLE-ADVANCED:INTERNAL=1
PERL_INCLUDE_PATH-ADVANCED:INTERNAL=1
PERL_LIBRARY-ADVANCED:INTERNAL=1

CMake prefix is /usr/local.

Comment 1 Vadim Zhukov 2013-07-02 23:23:52 UTC

Sorry, they are not same, I misdiffied output. Here are relevant parts of CMakeCache.txt of the new behaviour:

$ egrep '^([^/].*)?PERL' ../build-i386/CMakeCache.txt  
CUSTOM_PERL_SITE_ARCH_DIR:STRING=/usr/local/local/libdata/perl5/site_perl/i386-openbsd
PERL_EXECUTABLE:FILEPATH=/usr/bin/perl
PERL_INCLUDE_PATH:PATH=/usr/libdata/perl5/i386-openbsd/5.16.3/CORE
PERL_LIBRARY:FILEPATH=/usr/lib/libperl.so.13.0
PERL_EXECUTABLE-ADVANCED:INTERNAL=1
PERL_INCLUDE_PATH-ADVANCED:INTERNAL=1
PERL_LIBRARY-ADVANCED:INTERNAL=1

Comment 2 Andrew Crouthamel 2018-11-10 03:11:35 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Chris Burel 2018-11-10 06:38:08 UTC

I can't replicate this in the current development version.