Re: [perl #59112] Failing test in t/examples/library.t
James (): Can you report what results you are currently getting when you run: prove -v t/examples/library.t ? $ prove -v t/examples/library.t t/examples/library.t 1..4 ok 1 - examples/library/getopt_demo.pir ok 2 - examples/library/md5sum.pir 7.7 Failed to load libpcre current instr.: 'parrot;PCRE;init' pc 99 (library/pcre.pir:111) called from Sub 'parrot;PCRE;main' pc 215 (examples/library/pcre.pir:39) not ok 3 - examples/library/pcre.pir not ok 4 - ncurses_life.pir # TODO ncurses_life.pir not testable yet # Failed (TODO) test 'ncurses_life.pir' # at t/examples/library.t line 77. # Failed test 'examples/library/pcre.pir' # at t/examples/library.t line 67. # got: '' # expected: 'asdf =~ /as/ # 1 match(es): # as # ' # Looks like you failed 1 test of 4. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests Test Summary Report --- t/examples/library.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=1, Tests=4, 1 wallclock secs ( 0.01 usr 0.01 sys + 0.12 cusr 0.06 csys = 0.20 CPU) Result: FAIL
[perl #59112] Failing test in t/examples/library.t
On Wed Oct 22 12:52:39 2008, masak wrote: Just wanted to note that the reported problem does not occur for me anymore. In fact, I don't see the file t/examples/library.t among the tested files in the `make test` output. Neither does grep. Unfortunately, all that demonstrates is that we changed the list of tests run during 'make test' to exclude t/examples/*.t. The test file itself is still very much there. $ ls -l t/examples/library.t -rw-r--r-- 1 jimk jimk 2108 Jul 2 20:26 t/examples/library.t Can you report what results you are currently getting when you run: prove -v t/examples/library.t ? Thank you very much. kid51
Re: [perl #59112] Failing test in t/examples/library.t
Your point is very interesting. However, if you believe this issue merits more extended discussion, I would recommend you open up a new RT ticket, perhaps in the [RFC] category (or [RFP] or whatever it's called). I would like to keep the discussion in *this* RT focused on the issues Carl raised with respect to config step auto::pcre. We need to know what's happening. I see two possibilities: - The pcre library detected by the configure probe is static. Don't know what to do in that case, with static linkage the dynamic symbols needed for NCI may not be available, some static support for the library inside parrot may be required. - The library is dynamic but cannot be located at runtime. This can happen if is located in a place the dynamic linker does not search. In that case, the symbols can be found in the main process (at least in Linux) if the dynamic loading attempt fails. We can check this (in Linux, again), by looking for pcre in the output of: ldd parrot We must know what pcre library files are available, where are located, and if this place is searched by the dynamic linking at runtime (in Linux, listed in ldconfig configuration files). The problem can be just the lack of a libpcre.so symbolic link to libpcre.so.some_version_number Note that in the dynamic case, if the library can be found by the dynamic runtime linker we don't need any configure support at all. You can build --without-pcre and have pcre available anyway. -- Salu2
[perl #59112] Failing test in t/examples/library.t
Forgot to forward to list: On Thu Oct 02 18:37:05 2008, [EMAIL PROTECTED] wrote: On Wed Oct 01 16:09:41 2008, julianalbo wrote: I see a more generic problem. Several modules add lib links to the parrot executable. Makes sense to link static libraries if that is the intention, but is not convenient to link dynamics that can be, and are, dynamically linked at runtime. This way adds unneeded dependences to the binary packages. [snip] Your point is very interesting. However, if you believe this issue merits more extended discussion, I would recommend you open up a new RT ticket, perhaps in the [RFC] category (or [RFP] or whatever it's called). I would like to keep the discussion in *this* RT focused on the issues Carl raised with respect to config step auto::pcre. Thank you very much. kid51
[perl #59112] Failing test in t/examples/library.t
On Tue Sep 30 16:48:32 2008, masak wrote: James (): Let's start with an elementary question: What does Configure.pl say for you at this step: auto::pcre - Does your platform support pcre auto::pcre - Does your platform support pcreyes, 7.7. // Carl Heretofore I did not have PCRE installed on either Darwin or Linux. I just installed it on Debian Stable, which provided version 6.7, not 7.7: auto::pcre - Does your platform support pcreyes, 6.7. With this version installed, I could not reproduce the error you reported. See: http://smolder.plusthree.com/app/public_projects/tap_stream/5784/392 So could this be a problem with PCRE 7.7, or how it installs on your OS? Thank you very much. kid51
Re: [perl #59112] Failing test in t/examples/library.t
auto::pcre - Does your platform support pcreyes, 6.7. With this version installed, I could not reproduce the error you reported. See: http://smolder.plusthree.com/app/public_projects/tap_stream/5784/392 So could this be a problem with PCRE 7.7, or how it installs on your OS? The config test for pcre try to compile a test program. The pcre.pir dynamically loads the pcre library. So if, for example, you have only a static pcre lib, it will detect it but fails to use. -- Salu2
Re: [perl #59112] Failing test in t/examples/library.t
On Wednesday 01 October 2008 13:43:37 NotFound wrote: auto::pcre - Does your platform support pcreyes, 6.7. With this version installed, I could not reproduce the error you reported. See: http://smolder.plusthree.com/app/public_projects/tap_stream/5784/392 So could this be a problem with PCRE 7.7, or how it installs on your OS? The config test for pcre try to compile a test program. The pcre.pir dynamically loads the pcre library. So if, for example, you have only a static pcre lib, it will detect it but fails to use. That makes sense. Can we change the config test to link against a dynamic pcre? -- c
[perl #59112] Failing test in t/examples/library.t
On Wed Oct 01 13:58:32 2008, [EMAIL PROTECTED] wrote: On Wednesday 01 October 2008 13:43:37 NotFound wrote: The config test for pcre try to compile a test program. The pcre.pir dynamically loads the pcre library. So if, for example, you have only a static pcre lib, it will detect it but fails to use. That makes sense. Can we change the config test to link against a dynamic pcre? Patches welcome. I'm cc-ing ambs, who was the original contributor of this config step and the associated C probe, to see if he can help out. Thank you very much. kid51
Re: [perl #59112] Failing test in t/examples/library.t
The config test for pcre try to compile a test program. The pcre.pir dynamically loads the pcre library. So if, for example, you have only a static pcre lib, it will detect it but fails to use. That makes sense. Can we change the config test to link against a dynamic pcre? Patches welcome. I'm cc-ing ambs, who was the original contributor of this config step and the associated C probe, to see if he can help out. I see a more generic problem. Several modules add lib links to the parrot executable. Makes sense to link static libraries if that is the intention, but is not convenient to link dynamics that can be, and are, dynamically linked at runtime. This way adds unneeded dependences to the binary packages. Also, if the libraries are linked to the parrot executable or the parrot library makes no sense to fail if they can not be located at runtime. We need some way to know that the library is already linked and his symbols available, without forcing all modules that use a library to check for both cases. -- Salu2
Re: [perl #59112] Failing test in t/examples/library.t
James (): Let's start with an elementary question: What does Configure.pl say for you at this step: auto::pcre - Does your platform support pcre auto::pcre - Does your platform support pcreyes, 7.7. // Carl
[perl #59112] Failing test in t/examples/library.t
On Sat Sep 20 04:13:08 2008, masak wrote: In Parrot r31286: $ perl t/examples/library.t 1..4 ok 1 - examples/library/getopt_demo.pir ok 2 - examples/library/md5sum.pir 7.7 Failed to load libpcre current instr.: 'parrot;PCRE;init' pc 110 (library/pcre.pir:111) called from Sub 'parrot;PCRE;main' pc 279 (examples/library/pcre.pir:39) not ok 3 - examples/library/pcre.pir # Failed test 'examples/library/pcre.pir' # at t/examples/library.t line 67. # got: '' # expected: 'asdf =~ /as/ # 1 match(es): # as # ' Let's start with an elementary question: What does Configure.pl say for you at this step: auto::pcre - Does your platform support pcre Thank you very much. kid51
[perl #59112] Failing test in t/examples/library.t
# New Ticket Created by Carl Mäsak # Please include the string: [perl #59112] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=59112 In Parrot r31286: $ perl t/examples/library.t 1..4 ok 1 - examples/library/getopt_demo.pir ok 2 - examples/library/md5sum.pir 7.7 Failed to load libpcre current instr.: 'parrot;PCRE;init' pc 110 (library/pcre.pir:111) called from Sub 'parrot;PCRE;main' pc 279 (examples/library/pcre.pir:39) not ok 3 - examples/library/pcre.pir # Failed test 'examples/library/pcre.pir' # at t/examples/library.t line 67. # got: '' # expected: 'asdf =~ /as/ # 1 match(es): # as # ' not ok 4 - ncurses_life.pir # TODO ncurses_life.pir not testable yet # Failed (TODO) test 'ncurses_life.pir' # at t/examples/library.t line 77. # Looks like you failed 1 test of 4.
