Perl 6 - the future is here, just unevenly distributed

IRC log for #perl11, 2013-12-29

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 basiliscos than   yes, it could fit in.
00:03 Will_the_Chill oh I don't want to skip any tests  :)
00:04 basiliscos Will_the_Chill: no, not yours tests, but the tests of dependencies. It will run your tests, on installed-without-tests dependencies
00:05 Will_the_Chill yeah I understood what you meant
00:05 Will_the_Chill I want all tests run  :)
00:05 Will_the_Chill I'm a test-aholic, especially for RPerl dependencies
00:05 Will_the_Chill XD
00:09 basiliscos http://bpaste.net/show/162642/
00:09 basiliscos I got the same error: it can't found I::CPP
00:09 basiliscos I did all instructions
00:09 basiliscos and both - with symlink and with bulk's version
00:12 Will_the_Chill the symlink for Inline::Filters is a different issue than the installation of Inline::CPP
00:13 Will_the_Chill installing Inline::CPP is not unique to RPerl
00:13 Will_the_Chill I did not create Inline
00:13 Will_the_Chill that was ingy (he's on this channel)
00:13 Will_the_Chill so we need to somehow figure out why it is not installing Inline::CPP and/or not finding it after it is installed
00:15 basiliscos http://bpaste.net/show/162645/
00:15 basiliscos as you can see, the test example from I::CPP works well
00:17 basiliscos but your tests complain, that it can't be found. I think, that it expects some predefined location, or the error message is wrong ?
00:17 basiliscos how to track on which command it comlains ?
00:17 Will_the_Chill in your link here: http://bpaste.net/show/162642/
00:17 Will_the_Chill you will see this "If you have installed a support module for this language, try deleting the
00:17 Will_the_Chill # config-x86_64-linux-thread-multi-5.016003 file from the following Inline DIRECTORY, and run again:"
00:18 Will_the_Chill /home/nemo/rperl/_Inline
00:18 Will_the_Chill so please try to run `rm -Rf /home/nemo/rperl/_Inline`
00:18 Will_the_Chill and then find any other place you may have run a command that left behind an _Inline directory, then delete that one as well
00:18 Will_the_Chill then try again
00:19 basiliscos the same result. I execute the tests via : rm -Rf _Inline/; reset; perl -Ilib t/03_inline_cpp.t
00:20 Will_the_Chill um...
00:20 Will_the_Chill so Inline::CPP is installed correctly but RPerl's tests can't fidn it
00:20 Will_the_Chill *find it
00:20 Will_the_Chill haven't had that issue yet
00:21 Will_the_Chill try adding/modifying the -Ilib part of the perl command?
00:21 basiliscos OK, I moment
00:21 Will_the_Chill so you're running this as a non-perlbrew user, with a fresh local::lib?
00:21 basiliscos yes
00:21 Will_the_Chill and you ran the Makefile/cpan commands and it installed Inline::CPP into local::lib?
00:22 basiliscos yes
00:22 Will_the_Chill OH you have to set the env vars, and put them into .bashrc or re-set them manually for each new shell or xterm
00:23 Will_the_Chill this is an operating system and/or perl lib issue that is outside RPerl I think?
00:23 Will_the_Chill RPerl used to have "use lib" stuff but it was removed thanks to mst and replace w/ local::lib
00:24 basiliscos http://bpaste.net/show/162655/ - I think they are correct, isn't it?
00:24 basiliscos and the tests for I::CPP is executing well http://bpaste.net/show/162645/
00:26 Will_the_Chill wow I'm stumped
00:27 Will_the_Chill that's just weird
00:27 basiliscos OK, I almost fall asleep . :) Good luck for you, Will_the_Chill! We can try it tomorrow, if you have some ideas
00:27 Will_the_Chill okay, sounds good, thanks!  :)
00:55 bulk88 dalek bot never came back after it was kickbanned and unbannned, its owner's intervention is required, travis bot only signs in when a commit is pushed, then promptly signs off
00:57 bulk88 Inline installs ::C (included or dep, I dont remember), but ::CPP is a separate module/tarball I think that depends on Inline
00:57 Will_the_Chill yeah I think rurban is waiting for _sorear to return from vacation?
00:58 Will_the_Chill bulk88: basiliscos seems to have got Inline::CPP installed but for some reason RPerl wasn't finding it
00:58 Will_the_Chill he had a weird perlbrew setup
00:58 Will_the_Chill it has me stumped
00:58 Will_the_Chill and he's gone now
00:58 bulk88 cpan tools often will build deps for a module, and not install them
00:59 bulk88 cpan (the traditional one) has a habit of strictly following the META.* deps, so a build dep, won't be installed to the system perl, but the runtime dep will be
01:00 bulk88 confusion can result if the deps aren't perfectly specified, or if already installed into site
01:00 Will_the_Chill huh
01:00 bulk88 and the module tarball maintainer doesn't realize that the only reason the build, or make test, or runtime usage, works, is because of an already installed /site module
01:01 Will_the_Chill well it certainly confused me
01:01 bulk88 these are generic problems, not specific to what happened above with basiliscos which I dont fully understand enough to comment on
01:03 bulk88 ideally, to test a CPAN module, /site and /vendor should be removed from @INC or deleted from disk from non-main-system-perl
01:04 Will_the_Chill okay then
01:04 bulk88 I dont know what CONFIGURE_REQUIRES is, but my CPAN module uses a couple things in BUILD_REQUIRES for the make test, which are not required at runtime since the module only needs the BUILD_REQUIRES modules if you use some advanced features/method calls
01:05 Will_the_Chill ah, well, that does add a layer of complexity!
01:06 bulk88 I have it set up, if you want to use the fancy features of Win32::API, you need to "use" the module (Math::Int64), yourself, before doing the optional Win32::API method call to turn on Int 64s
01:06 bulk88 otherwise you get undefined sub errors out of the Win32::API meth call
01:09 Will_the_Chill cool
01:09 Will_the_Chill I guess?  :)
01:09 bulk88 some people might code up, where, during require/import, the globs or $VERSION of a partner module are probed, if they aren't there, stubs can be installed that will lazy load or an AUTOLOAD function in that package for the unloaded module can be created that will do a require&import on the first sub call to that not yet loaded module
01:10 bulk88 too many modules on CPAN, on a fresh perl, there are 10-30 tarballs downloaded and built when you want to install 1 module
01:11 Will_the_Chill haha that sucks
01:11 bulk88 rperl's deps are an example of 10-30 tarballs
01:11 bulk88 rperl has only I think 2 or 3 deps specified, but they bloom into like 20 tarballs and 30 mins of building and make tests
01:13 Will_the_Chill right
01:13 Will_the_Chill that is correct
01:14 bulk88 I know on CPAN, there are a couple "App::bulk88smodulestack" modules which list all the favorite modules of a particular perl programmer, so that particular perl programmer can make any perl install feel like home in 1 command line, now if one of that programmer's CPAN modules list a "App::bulk88smodulestack" as a dep, oh boy
01:15 bulk88 lesson of story, I'm sure a couple of those deps in rperl's deps can be thinned out, but its alot of work, with not enough reword
01:15 bulk88 *deps of rperl's deps
01:15 bulk88 *reward
01:16 Will_the_Chill huh
01:16 Will_the_Chill interesting
01:16 Will_the_Chill I wonder who that programmer is
01:16 Will_the_Chill ;)
01:17 bulk88 http://search.cpan.org/search?mode=all&query=belike
01:18 bulk88 the personal module stacks live in Task::BeLike, not App:: as I thought
01:19 Will_the_Chill yes I see that, cool stuff
07:23 mst joined #perl11
09:04 basiliscos joined #perl11
09:11 ilbot2 joined #perl11
09:11 Topic for #perl11 is now Perl5 + Perl6 == Perl11; # http://irclog.perlgeek.de/perl11/
14:33 basiliscos joined #perl11
17:23 Will_the_Chill basiliscos: howdy!  :)
17:24 Will_the_Chill basiliscos: if you run this command it will tell you which Inline::CPP module your system is finding...    'perldoc -l Inline::CPP'
17:26 basiliscos Will_the_Chill: Hello! 1 moment
17:28 basiliscos Will_the_Chill: http://bpaste.net/show/162806/ is is OK
17:31 Will_the_Chill and nemo is for sure a non-perlbrew user account?
17:31 Will_the_Chill please run 'perldoc -l Inline::Filters'
17:32 basiliscos yes
17:32 basiliscos http://bpaste.net/show/162808/
17:34 Will_the_Chill please run 'ls -lah /home/nemo/perl5/lib/perl5/Inline/'
17:37 basiliscos http://bpaste.net/show/162809/
17:42 Will_the_Chill okay there is an issue I have identified
17:43 Will_the_Chill I'm still slightly ignorant of what all mst did to transform the system into using local::lib
17:43 Will_the_Chill :)
17:43 Will_the_Chill you should not have any Filters.pm file in local::lib
17:43 Will_the_Chill so /home/nemo/perl5/lib/perl5/Inline/Filters.pm should not exist
17:44 Will_the_Chill or at least not for the purposes of RPerl
17:44 Will_the_Chill instead, RPerl should be using the file PATH_TO_RPERL/lib/Inline/Filters.pm
17:44 Will_the_Chill which is my hand-patched file
17:45 Will_the_Chill so it is now wrong to do any of the symlink stuff
17:45 Will_the_Chill which I didn't realize until I talked to mst after you left last night
17:46 basiliscos so, I should try just to delete home/nemo/perl5/lib/perl5/Inline/Filters.pm  ?
17:47 Will_the_Chill or just rename it something else
17:47 Will_the_Chill that's my only lead so far
17:47 Will_the_Chill actually that's not true
17:48 Will_the_Chill mst & bulk88 both talked to me about how some modules may not load properly due to weird mis-configuration s
17:48 Will_the_Chill which can lead to system-wide CPAN broken-ness
17:49 basiliscos I deleted it, but no result :)
17:49 Will_the_Chill no result meaning RPerl still can't find Inline::CPP just like before?
17:49 basiliscos yes
17:49 Will_the_Chill dang well then I'm back to being stumped
17:50 Will_the_Chill you could try running:      perl -e 'use Inline::CPP ();'
17:50 Will_the_Chill or even without the empty parens just to see if Inline will throw the proper error
17:50 Will_the_Chill with empty parens, on success, gives no output
17:51 basiliscos http://bpaste.net/show/162812/
17:51 Will_the_Chill without empty parens, on succesful loading of Inline::CPP, gives custom error
17:51 Will_the_Chill It is invalid to use 'Inline::CPP' directly.
17:51 Will_the_Chill well that looks right
17:51 Will_the_Chill so we're back to the same conundrum
17:52 Will_the_Chill that Inline::CPP is installed but RPerl isn't finding it
17:52 Will_the_Chill MOST LIKELY because of some perlbrew weirdness
17:52 basiliscos I think it was bad idea to use I::F, because so many fails reports from from cpanm tester
17:52 basiliscos no
17:52 basiliscos I don't have perbrew on that account
17:52 basiliscos I launched an bebug
17:52 Will_the_Chill perlbrew may have somehow hosed your whole system
17:53 Will_the_Chill "bad idea to use I::F"    there is no alternative
17:53 Will_the_Chill and I patched it and bulk88 uploaded the unauthorized version and mst is making me the new I::F maint so we can clean it up
17:53 basiliscos Here is an stacktrace http://bpaste.net/show/162813/
17:53 Will_the_Chill the bad idea would have been to NOT use it because then RPerl would  not have worked at all
17:54 basiliscos in config object, I see available languages - C only
17:54 Will_the_Chill yes Inline is loaded but it can't find Inline::CPP
17:55 Will_the_Chill confirming our previous knowledge
17:55 Will_the_Chill that it is borked  ;)
17:57 Will_the_Chill okay my current train of thought:
17:57 Will_the_Chill wipe local::lib:       rm -Rf /home/nemo/perl5
17:58 Will_the_Chill then try to load Inline, I::C, I::CPP, I::F again
17:58 Will_the_Chill and do system-wide 'find' commands as well
17:58 Will_the_Chill to eradicate any of these files from system-wide or perlbrew or any other install
17:58 basiliscos wait a minute
17:58 Will_the_Chill do the same to find and eradicate all RPerl files
17:59 Will_the_Chill totally wipe all RPerl, Inline, etc files
17:59 Will_the_Chill that includes all other RPerl deps shown in the RPerl Makefile
17:59 Will_the_Chill such as Parse::RecDescent
17:59 basiliscos I have found that's config: _Inline/config-x86_64-linux-thread-multi-5.016003 : http://bpaste.net/show/162814/
17:59 Will_the_Chill I mean really go hardcore and search the entire filesystem for every single possibly-offending file
17:59 Will_the_Chill any directory that is _Inline must be removed
17:59 basiliscos how it appears? Why C++ isn't mentioned there?
18:00 basiliscos Yes, I know
18:00 basiliscos but how it appears with wrong conent?
18:00 Will_the_Chill _Inline is the directory automatically created by the Inline::* modules when they compile stuff
18:00 Will_the_Chill whatever is created in there is magic and I don't have any knowledge or control of it
18:01 Will_the_Chill that's why all my RPerl experimental commands are prefaced with 'rm -Rf _Inline;'
18:01 Will_the_Chill so that we wipe that directory every time
18:01 Will_the_Chill which forces a recompile every time
18:01 basiliscos ok
18:01 Will_the_Chill once you reach a point where the code is stable and you don't need a recompile for every run, just don't do the 'rm -rf _Inline;' any more
18:02 Will_the_Chill so ANYWAY be super thorough and find all RPerl dependency files on the while operating system
18:02 Will_the_Chill then we will create a new from-scratch unix user account and run everything through there
18:02 Will_the_Chill not using nemo or any other pre-existing account
18:02 Will_the_Chill because basically I think your system-wide CPAN is messed up
18:03 Will_the_Chill and this is the only way I can think to even try to fix it
18:03 Will_the_Chill I may not be successful in leading you on how to do this
18:03 Will_the_Chill but mst is not online right now
18:03 Will_the_Chill so I'm doing my best in his absence :)
18:05 basiliscos I don't have system-wide CPANM modules like Inline*
18:06 basiliscos http://bpaste.net/show/162815/
18:06 Will_the_Chill 'sudo find / | grep nline 2> /dev/null'
18:08 basiliscos you don't trust me. Ok, 1 moment.
18:08 Will_the_Chill haha
18:08 Will_the_Chill no I do trust you, I've just run out of idea!  ;)
18:09 Will_the_Chill and then also 'sudo find / | grep RPerl 2> /dev/null'
18:12 Will_the_Chill please  :)
18:16 basiliscos it still doing the 1st seach
18:17 Will_the_Chill okay
18:18 Will_the_Chill it may be finding a lot of non-perl files but that's fine
18:18 Will_the_Chill :)
18:32 basiliscos http://bpaste.net/show/162823/
18:33 Will_the_Chill "/Inline.pm" found 11 times in that document
18:34 Will_the_Chill "/CPP.pm" found 6 times
18:34 Will_the_Chill "/C.pm" found 9 times
18:35 Will_the_Chill "/Filters.pm" found 26 times, including some times in RPerl dirs
18:35 Will_the_Chill so there is no way in hades to know which ones of those 52 files we're touching or missing
18:36 Will_the_Chill we must eradicate them all
18:36 Will_the_Chill and all associated installations
18:36 Will_the_Chill and dependencies
18:36 Will_the_Chill nuke 'em
18:36 Will_the_Chill CAREFULLY of course  :)
18:36 Will_the_Chill what I'm saying is we're trying to debug a spaghetti OS config by having so many different versions and locations of each of these files
18:37 Will_the_Chill and that spaghetti debugging will probably not work
18:37 Will_the_Chill so we need to get rid of the noodles
18:37 basiliscos no, sorry.Only relevant are for /usr/lib and /home/nemo ones
18:37 Will_the_Chill well start by cleaning out the ones you know should not be there
18:37 Will_the_Chill and that's a start at least!
18:38 Will_the_Chill are you using any of the perl Inline modules for any of your other projects?
18:38 basiliscos no
18:38 Will_the_Chill in other words, should Inline or any Inline stuff legitimately be installed anywhere on your system other than for use by RPerl?
18:39 Will_the_Chill so then we really should be able to completely remove all Inline from everywhere on your system, without negatively affecting anything, because Inline should only be there for RPerl anyway?
18:41 basiliscos I'll remove http://bpaste.net/show/162827/ all that dirs, except the last one, right?
18:42 Will_the_Chill the first step should have already been 'rm -Rf /home/nemo/perl5' before even running the 'find' commands
18:43 basiliscos no
18:43 Will_the_Chill immediately followed by 'rm -Rf /home/nemo/rperl'
18:43 basiliscos it will delete all dependencies
18:43 Will_the_Chill yes
18:43 basiliscos it took about 1 hour to install all of them yesterday
18:43 Will_the_Chill we want to delete everything related to RPerl off your whole system
18:43 Will_the_Chill oh
18:43 Will_the_Chill well then I don't know what to say
18:44 basiliscos the account was fresh yesturday
18:44 basiliscos (nemo account)
18:44 Will_the_Chill hmm
18:44 basiliscos and, as you can see, there is no any "Inline::*" on system, only on my dev-account 'dmol'
18:44 Will_the_Chill my only response is that while the nemo account may have been clean, obviously there are lots of places where Inline is installed other than /home/nemo
18:44 Will_the_Chill yes
18:44 Will_the_Chill okay
18:44 Will_the_Chill well dang
18:45 Will_the_Chill this is going to end up being some kind of obvious DUH! thing
18:45 Will_the_Chill but I am stumped
18:45 Will_the_Chill we should wait for mst so I don't waste any more of your time
18:45 basiliscos ok.
18:45 basiliscos I'll try do debug meanwhile :)
18:46 Will_the_Chill cool!  :)
18:46 Will_the_Chill sorry I couldn't fix it.  :(
18:55 bulk88 inline probably hard codes what partner modules were installed into a .pm config file
18:56 Will_the_Chill OH GOOD maybe bulk88 can help!
18:56 bulk88 since you are doing, 1 perl binary, many per user /lib'es, inline might be reading the system /lib inline config file and not the per user inline config file
18:57 Will_the_Chill hey there's an idea
18:57 Will_the_Chill WARNING: bulk88 is on Windows and basiliscos is on Linux  ;)
18:57 bulk88 I dont know the name of the .pm that is being used as the config file of .pm
18:57 bulk88 yes I know that
18:57 Will_the_Chill well I'm fresh out of hot ideas
18:57 bulk88 Im not sure the technical details of what perlbrew does, I know why you use it, but not its implementation
18:58 Will_the_Chill I messaged mst so whenever he wakes up later today he might be able to help
18:58 bulk88 there was one post by basiliscos which said "it is invalid to use I::CPP directly"
18:58 Will_the_Chill perlbrew is similar to rurban's perlall and also another one called plenv
18:58 Will_the_Chill YES it is invalid to use I::CPP directly
18:58 Will_the_Chill 'use Inline::CPP;' is wrong
18:59 bulk88 you didn't pursue the correct fix which was a different -e" use something" not -e "use I::CPP"
18:59 Will_the_Chill 'use Inline::CPP ();' is allowed because it skips import
18:59 Will_the_Chill I just gave it to you
18:59 Will_the_Chill perl -e 'use Inline::CPP ();'
18:59 Will_the_Chill there that's legit
18:59 bulk88 that isn't the correct fix
18:59 Will_the_Chill oh well maybe I don't know what you're trying to fix
19:00 Will_the_Chill I was just saying that's a way to do a quick test and see if your perl is finding/loading I::CPP
19:00 bulk88 the problem is, you want to use I::CPP through its public interface, which is from I::, disabling the warning on I::CPP::import wont help in solving why I:: doesn't see I::CCP
19:01 bulk88 -e"use Inline CPP;" would be correct
19:02 Will_the_Chill perl -e 'use Inline CPP;'
19:02 Will_the_Chill No source code in DATA section for Inline 'CPP' section.
19:03 Will_the_Chill perl -e 'use Inline CPPd;'
19:03 Will_the_Chill No source code in DATA section for Inline 'CPPd' section.
19:03 Will_the_Chill nope I don't think that does what you think it does
19:03 Will_the_Chill IOW I don't think it actually tests for anything useful
19:04 bulk88 "No source code in DATA section for Inline 'CPP' section." im not sure with that message it even tried to load I::CPP.pm
19:05 Will_the_Chill it didn't, that's why I showed you the "CPPd" version
19:05 Will_the_Chill there is no module "CPPd", but it gave the same error as the legit module "CPP"
19:05 Will_the_Chill indicating that it did not do anything useful
19:07 basiliscos I don't know, weather is is relevent, but I found in debug the following: it loads Inline.pm from $rperl/lib/ , but the function Inline::check_config_file is loaded from perl5/lib/perl5/auto/Inline/check_config_file.al
19:07 bulk88 yes, so inline's plugin framework bailed out before even trying to load the language handling plugin
19:08 basiliscos so, I jumps between different codes of the same file (Inline.pm)
19:08 bulk88 I have no idea what a .al is because im on Windows
19:08 basiliscos probably, I should delete $rperl/lib/Inline.pm
19:09 bulk88 no, my Inline also has .al'es
19:10 basiliscos Yes!!!
19:10 basiliscos I'm the best!
19:10 basiliscos I deleted the $rperl/lib/Inline.pm and $rperl/lib/Inline/C.pm
19:10 basiliscos and now the tests are passing
19:11 basiliscos I think Inline.pm tries to locate available languages in the same directory, where it is located
19:11 basiliscos and it founds only C.pm
19:12 basiliscos because they are in $rperl/lib/
19:12 basiliscos but when I try to use examples for I::CPP, they work, because Inline.pm is located in $local::lib, where I::CPP is located too
19:13 basiliscos that's why the examples working
19:14 basiliscos Will_the_Chill: so, you should either delete Inline.pm and I::C.pm from your rperl/lib, or to put there I:CPP
19:14 basiliscos I think the 1st way is more correct (shipping libraries is not perl-way)
19:17 basiliscos Will_the_Chill: so, t/03_inline_cpp.t passes
19:17 basiliscos t/04_type_scalar.t :  Looks like you failed 6 tests of 273.
19:18 basiliscos t/05_type_array.t - passes
19:19 basiliscos t/06_type_hash.t - passes
19:21 basiliscos t/08_precompiled_sort.t - passes
19:21 basiliscos t/07_oo_inherit.t - skipped
19:22 Will_the_Chill just a moment
19:23 Will_the_Chill AH nice
19:23 Will_the_Chill great job everybody!
19:24 Will_the_Chill what are the failing tests?
19:24 basiliscos http://bpaste.net/show/162837/ - here is the output of t/04_type_scalar.t
19:27 Will_the_Chill oh good your tests are actually throwing less errors than mine which is why it fails
19:27 Will_the_Chill it may not be correct but it is not detrimental
19:27 Will_the_Chill so good!  :)
19:27 basiliscos I hope that will speed up release a bit :)
19:28 Will_the_Chill yes I told mst to take a look at your data and he will help me decide what to do, thank you so much for debugging!  :D
19:28 basiliscos may be it depends on installed gcc version somehow ?
19:28 Will_the_Chill it does need a compiler that supports C++11
19:29 Will_the_Chill bulk88 and I have had issues with his Windows system needing C++11, still working on that one, haha!  :)
19:29 basiliscos my gcc version is 4.7.3
19:29 basiliscos I don't know, which c++ specification it supports, through.
19:30 Will_the_Chill well if your t/06_type_hash.t tests pass, then you have C++11 enabled
19:30 basiliscos I think it is a good idea to do some test, which check for C++11 features for correctness
19:31 basiliscos Will_the_Chill: which c++ compiler do you have ?
19:31 Will_the_Chill well 06_type_hash.t IS the test for C++11 correctness
19:31 Will_the_Chill I have gcc 4.5.2
19:31 basiliscos AFAIK, gcc does not fully conforms to C++ v.11  specifications, but partially supports some of them
19:32 Will_the_Chill it will be a long time before everybody fully conforms to C++11 standards, I'm not worried about that
19:32 Will_the_Chill as long as RPerl's tests pass!
19:32 basiliscos :)
19:33 Will_the_Chill basiliscos: take a look at the files bin/development/precompiled_sort_test.pl and lib/RPerl/Algorithm/Sort/Bubble.cpp
19:33 Will_the_Chill it will show you the hand-compiled code
19:33 Will_the_Chill now I must get back to finish v1.0!  :)
19:33 Will_the_Chill just ping me here on IRC if you need my help
19:39 basiliscos Oh, it seems too complex at the first glance. OK, then, I'll watch for the sources https://github.com/wbraswell/rperl, and if you'll follow my advice to delete Inline.pm and C.pm, or find any other solution to make it work, than I'll try to setup travis-ci to build it :)
19:40 Will_the_Chill awesome!  I'm sure mst will tell me the best plan and then we'll go from there so you can do travis.  :)
20:14 BenGoldberg joined #perl11
20:15 BenGoldberg left #perl11
20:39 stevan joined #perl11
20:40 stevan joined #perl11
20:42 stevan joined #perl11
20:52 mst basiliscos: your reports from 90mins ago are what I'd expect to see with a clean local::lib
20:52 mst basiliscos: and a fresh checkout
20:53 mst Will_the_Chill: if it passes without, why did you have Inline and Inline/C.pm in the repo anyway?
20:54 Will_the_Chill Inline::Filters is my hand-patched version
20:54 Will_the_Chill there may be some of my code in Inline::C as well I'd have to check
20:55 mst dude. I asked about Inline.pm and Inline/C.pm
20:55 mst telling me about Inline::Filters in response is ...
20:55 Will_the_Chill yes I just checked
20:55 Will_the_Chill I have debugging code in both of those 2 files
20:56 mst but they're otherwise identical to the current versions on cpan?
20:56 Will_the_Chill YES
20:56 Will_the_Chill oops sorry caps
20:56 Will_the_Chill yes they are the same as CPAN with debugging
20:57 Will_the_Chill we don't want to trash my versions though, because it is at least a start on debugging some long-standing Inline issues
20:57 Will_the_Chill we just want to disable them and save them for future use somehow
20:58 mst we're not going to trash yours in that case
20:58 mst they can stay in lib/ fine
20:58 Will_the_Chill okay
20:59 Will_the_Chill I knew you'd have the answer
20:59 Will_the_Chill :)
20:59 Will_the_Chill so do I need to do anything?
20:59 mst well, I have more interesting questions and a desire to experiment anyway
20:59 Will_the_Chill well then!  more interesting indeed!  XD
20:59 mst since I have Inline/CPP.pm in a local::lib, and your lib/Inline.pm untouched, and my setup works
20:59 Will_the_Chill yes I was just thinking it is still weird, eh?
21:00 Will_the_Chill like, I'm using local::lib too, and my setup works
21:00 mst right. deleting stuff out of lib/ shouldn't've fixed basiliscos' setup
21:00 mst I mean, it should either have been broken before and after the rm, or working before and after
21:01 basiliscos no, it works after removing lib/Inline.pm and lib/I::C.pm
21:01 Will_the_Chill a-ha, good point!  and now I think you're over my head.  :/
21:03 mst basiliscos: interesting question: what happens if you put them back?
21:03 mst git checkout lib/Inline.pm; git checkout lib/Inline/C.pm
21:03 mst and then re-run the tests
21:03 basiliscos I expect: no CPP can be found.
21:03 basiliscos just a second I'll check that
21:05 basiliscos Yes.  I currently only know about the following languages: C
21:05 basiliscos mst: see my explanation above.
21:05 basiliscos for that case
21:06 basiliscos I have to go. Good luck for you! See you tomorrow!
21:06 mst basiliscos: what explanation?
21:06 bulk88 read the backscroll
21:07 mst the backscroll includes "I think Inline.pm is only looking in its own @INC element"
21:07 mst that's not an explanation. that's a wild ass guess
21:07 mst and it doesn't explain why my system, and Will, works perfectly
21:07 mst an explanation has to actually explain something
21:08 mst a guess that doesn't fit the facts isn't the same thing
21:08 bulk88 Ill try to find the basilicous line it will take a few minutes
21:10 Will_the_Chill wow basiliscos really bailed on us right when we were getting somewhere, haha!  :P
21:10 bulk88 http://paste.scsys.co.uk/288200
21:12 bulk88 as far as I understand, basiliscos was claiming Inline:: uses a relative path to Inline.pm to find other language Inline plugins
21:12 bulk88 not @INC
21:14 mst bulk88: I'd already found that line
21:14 mst I just quoted that line
21:14 mst and it's still a guess that doesn't actually fit the facts
21:14 mst so it's still not an explanation
21:15 Will_the_Chill right
21:15 Will_the_Chill a guess
21:22 bulk88 I would recommend basiliscos putting a $DB::single=1; in Inline::check_config_file and stepping it himself to solve the problem
21:23 mst you're welcome to talk him through that
21:23 mst and it'd be appreciated if you do
21:24 mst (me and the debugger do not get on, I'd love the results but wouldn't be able to help with the process :)
21:26 Will_the_Chill and I'm already pretty much lost  D:
21:26 Will_the_Chill I really did try my best!  :/
21:29 bulk88 mst, that is not going to happen, since I've never used Perl's CLI debugger, only Komodo's GUI Perl debugger
21:30 mst ok, well in that case I think perhaps you shouldn't recommend something that none of us know how to do!
21:32 Will_the_Chill HAHA
21:33 Will_the_Chill oh boy
21:33 Will_the_Chill yeah
21:33 Will_the_Chill good point
21:34 Will_the_Chill we should prolly just wait for basiliscos to come back

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary