doesn't look like an ikiwiki bug

[git.ikiwiki.info.git] / doc / bugs / 2.45_Compilation_error.mdwn

diff --git a/doc/bugs/2.45_Compilation_error.mdwn b/doc/bugs/2.45_Compilation_error.mdwn
index d6040904a64c33467e2a2a5e9dd40deed7b1ea73..63147b6560ced3a9a24478196b0d003919b590b2 100644 (file)
--- a/doc/bugs/2.45_Compilation_error.mdwn
+++ b/doc/bugs/2.45_Compilation_error.mdwn
@@ -174,8 +174,25 @@ command line, the command succeeds. In other words, if I run
 
 then it works perfectly.
 
 
 then it works perfectly.
 

+> Well, that's just weird, because `libdir` is handled by code in IkiWiki.pm.
+> So I don't see how setting it could affect its searching for IkiWiki.pm at all,
+> actually. It could only affect its searching for files loaded later. Anyway,
+> can I get a strace of it succeeding this way?
+> 
+> Also, can you show me the first 15 lines of your `ikiwiki.out`? It's occurred to me
+> you might have an unusual `use lib` line in it.
+

 By the way, I'm running Arch linux. The perl build script is a bit long, but I
 see they install a patch to modify @INC: <http://repos.archlinux.org/viewvc.cgi/perl/repos/core-i686/perl-5.10.0-archlinux-inc-order.patch?revision=1&view=markup>
 
 Would you suggest I try rebuilding perl without this patch? Debian has a huge perl patch (102K!);
 it's not straightforward for me to see if they do something similar to Arch.
 By the way, I'm running Arch linux. The perl build script is a bit long, but I
 see they install a patch to modify @INC: <http://repos.archlinux.org/viewvc.cgi/perl/repos/core-i686/perl-5.10.0-archlinux-inc-order.patch?revision=1&view=markup>
 
 Would you suggest I try rebuilding perl without this patch? Debian has a huge perl patch (102K!);
 it's not straightforward for me to see if they do something similar to Arch.

+
+> I think Debian has a similar patch.
+
+---
+
+[[done]] -- apparently this was a problem due to a distribution's
+customisation to perl, or something. Seems to late now to track down what,
+unfortunatly. And ikiwiki's Makefile no longer uses the "-libdir" switch
+that seemed to trigger the bug. --[[Joey]]