On Tue, 9 Sep 2008, James Keenan via RT wrote:
On Tue Sep 09 15:14:36 2008, [EMAIL PROTECTED] wrote:
Generally agreed. In this case, hold this ticket for the I/O milestone,
which is next (sometime in the next few days). I've added it to the I/O
tasklist.
In the meantime, let's
On Wed Sep 10 09:30:37 2008, doughera wrote:
That's another easy one. The test assumes that all platforms have -lrt
and that all platforms have to link with it for this test. Your system
clearly doesn't have -lrt, so the link fails. If you just delete the
line
that adds in -lrt, I'll
On Wed, 10 Sep 2008, James Keenan via RT wrote:
On Wed Sep 10 09:30:37 2008, doughera wrote:
That's another easy one. The test assumes that all platforms have -lrt
and that all platforms have to link with it for this test. Your system
clearly doesn't have -lrt, so the link fails.
On Sat, 6 Sep 2008, chromatic wrote:
On Saturday 06 September 2008 20:19:56 James Keenan via RT wrote:
test_17787.c: In function 'main':
test_17787.c:45: error: 'SIGRTMIN' undeclared (first use in this function)
test_17787.c:45: error: (Each undeclared identifier is reported only once
On Tue, Sep 09, 2008 at 08:46:33AM -0400, Andy Dougherty wrote:
Parrot's also not using AIO anywhere either, so the whole probe is kind of
pointless right now. Mainly, I was just hoping that a minor fix would
help solve Patrick's problem of Configure.pl hanging during the aio probe.
I
On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty [EMAIL PROTECTED] wrote:
Parrot's also not using AIO anywhere either, so the whole probe is kind of
pointless right now.
Instead of spending time fixing a probe that isn't being used, we
should rip it out. If we eventually need it again, we can
On Tue, 9 Sep 2008, Will Coleda wrote:
On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty [EMAIL PROTECTED] wrote:
Parrot's also not using AIO anywhere either, so the whole probe is kind of
pointless right now.
Instead of spending time fixing a probe that isn't being used, we
should rip it
On Tue Sep 09 05:57:40 2008, coke wrote:
On Tue, Sep 9, 2008 at 8:46 AM, Andy Dougherty
[EMAIL PROTECTED] wrote:
Parrot's also not using AIO anywhere either, so the whole probe is
kind of
pointless right now.
Instead of spending time fixing a probe that isn't being used, we
should rip
Will Coleda wrote:
Instead of spending time fixing a probe that isn't being used, we
should rip it out. If we eventually need it again, we can start from
here, but there's no point in probing for features that we never use.
It's wasting developer (and less importantly, CPU) time better spent
On Tue Sep 09 15:14:36 2008, [EMAIL PROTECTED] wrote:
Generally agreed. In this case, hold this ticket for the I/O milestone,
which is next (sometime in the next few days). I've added it to the I/O
tasklist.
In the meantime, let's get Andy's patch applied (if it isn't already).
I
On Tue Sep 09 18:22:30 2008, [EMAIL PROTECTED] wrote:
I extracted the attached patch from email text and applied it in r30946.
For some reason, the first attachment -- Andy's patch -- didn't get
attached. Trying again.
diff -r -u parrot-current/config/auto/aio/aio.in
On Sat Sep 06 20:55:36 2008, [EMAIL PROTECTED] wrote:
... or we could use SIGUSR for the tests, I suppose. We're not using
real-time signals elsewhere in Parrot right now.
All I can really say at this point is, Patches welcome. From my
googling about SIGUSR, it appears we'd have to trap
On Fri, 5 Sep 2008, James Keenan via RT wrote:
On Thu Sep 04 19:22:56 2008, [EMAIL PROTECTED] wrote:
FWIW, here is a data point: What happens on my Darwin/PPC (10.4) Mac at
auto::aio:
On Darwin, Configure.pl reports that AIO is unsupported.
Follow-up question: If I 'locate aio'
On Sat Sep 06 16:46:08 2008, doughera wrote:
... what *else* would I need to have AIO available on Darwin?
It looks like you already have it available. If you try with my patch in
verbose mode, what, exactly, goes wrong such that Configure.pl concludes
AIO is unsupported?
See
On Saturday 06 September 2008 20:19:56 James Keenan via RT wrote:
On Sat Sep 06 16:46:08 2008, doughera wrote:
... what *else* would I need to have AIO available on Darwin?
It looks like you already have it available. If you try with my patch in
verbose mode, what, exactly, goes wrong
This is a patch in the sense of bandaid. What is it about the letter
'K' that means that this probe gives sloppy results on Kubuntu when on
Ubuntu it has built cleanly for me every day
Something to do with Gnome, since that's the major difference between the
two?
--
Email and
This is a patch in the sense of bandaid. What is it about the letter
'K' that means that this probe gives sloppy results on Kubuntu when on
Ubuntu it has built cleanly for me every day since I started
Something to do with KDE vs Gnome, since that's the major difference?
Perhaps KDE's
On Thu, 4 Sep 2008, Patrick R. Michaud wrote:
On Thu, Sep 04, 2008 at 04:52:34PM -0700, James Keenan via RT wrote:
I applied the patch attached, aio.in.revised.patch.txt, in r30771. I
set the 'sleep' to 4 seconds. All the tests have been reactivated.
Thanks.
This is a patch in the
I'll try this out on Darwin and (Debian) Linux this weekend and see what
happens. Thanks.
On Fri Sep 05 10:17:30 2008, doughera wrote:
This patch takes the following small steps:
First, I replaced the
retval = *(int*)i-si_ptr;
line by
retval = *(int*)i-si_value.sival_ptr;
I've never fiddled with this stuff before, but it looks like the
si_ptr
#define is not
On Thu Sep 04 19:22:56 2008, [EMAIL PROTECTED] wrote:
FWIW, here is a data point: What happens on my Darwin/PPC (10.4) Mac at
auto::aio:
On Darwin, Configure.pl reports that AIO is unsupported.
Follow-up question: If I 'locate aio' on my Mac and come up with this
(excerpted) list of
I just wanted to comment that I see this problem on my Kubuntu system as
well -- when running Configure.pl, I consistently get to the step for
AIO and things hang (until I press control-C):
...
auto::socklen_t - Determine whether there is
socklen_tyes.
auto::env -
On Thu Sep 04 06:33:41 2008, pmichaud wrote:
I just wanted to comment that I see this problem on my Kubuntu system as
well -- when running Configure.pl, I consistently get to the step for
AIO and things hang (until I press control-C):
...
auto::socklen_t - Determine whether there is
In r30754 I temporarily SKIPped most of the tests in
t/steps/auto_aio-01.t so that you can have a free hand in patching
auto::aio.
On Thu, Sep 04, 2008 at 08:31:10AM -0700, James Keenan via RT wrote:
On Thu Sep 04 06:33:41 2008, pmichaud wrote:
I just wanted to comment that I see this problem on my Kubuntu system as
well -- when running Configure.pl, I consistently get to the step for
AIO and things hang (until I press
On Thu Sep 04 11:26:44 2008, pmichaud wrote:
It does cause the auto::aio step to continue after about 10 seconds
with a message of wrong signal.
1. I think 10 seconds might be a bit too long -- 4 or 5 might be better.
2. It would be nice if wrong signal was suppressed, or otherwise
On Thu, Sep 04, 2008 at 04:52:34PM -0700, James Keenan via RT wrote:
I applied the patch attached, aio.in.revised.patch.txt, in r30771. I
set the 'sleep' to 4 seconds. All the tests have been reactivated.
Thanks.
This is a patch in the sense of bandaid. What is it about the letter
'K'
FWIW, here is a data point: What happens on my Darwin/PPC (10.4) Mac at
auto::aio:
On Darwin, Configure.pl reports that AIO is unsupported. If I hack up
config/auto/aio.pm to print the content of the $@ inside
_first_probe_for_aio() -- i.e., expose what the C probe in
config/auto/aio/aio.in
James Keenan via RT wrote:
On Mon Aug 25 13:15:16 2008, [EMAIL PROTECTED] wrote:
Generally recommend attaching patches as files ending in .patch (as
documented in docs/submissions.pod) for the sanity of the patch
monsters.
Well, since it's in the docs, I will withdraw the suggestion.
On my OpenSuse, it looks like this:
auto::aio - Does your platform support AIO...wrong signal
..done.
So the fact that it exits the loop early, just makes it continue to the wrong
signal indication, and that marks it as not supported. After all it did not
meet the
On Monday 25 August 2008, James Keenan via RT wrote:
On Thu Aug 14 06:03:27 2008, [EMAIL PROTECTED] wrote:
On my computer (OpenSuse 11.0) the Parrot Configure.pl hangs forever
when
checking for platfom support for AIO.
It appears to be a neverending sleep(1) loop in the check.
In the
On Tue Aug 26 06:15:19 2008, [EMAIL PROTECTED] wrote:
On Monday 25 August 2008, James Keenan via RT wrote:
1. After you run 'perl Configure.pl' with this patch on your box,
what
do you get for this:
grep -ni AIO lib/Parrot/Config/Generated.pm
AIO is not in the file.
(I am not
On Thu Aug 14 06:03:27 2008, [EMAIL PROTECTED] wrote:
On my computer (OpenSuse 11.0) the Parrot Configure.pl hangs forever
when
checking for platfom support for AIO.
It appears to be a neverending sleep(1) loop in the check.
In the patch I have added a countdown to make it exit after some
James Keenan via RT wrote:
3. For future reference, submit bug reports to:
[EMAIL PROTECTED] I recommend beginning Subject line with:
[BUG]. And I recommend submitting patches as email attachment ending in
: .txt (because that seems to render best in browsers, mail, news
interfaces).
On Mon Aug 25 13:15:16 2008, [EMAIL PROTECTED] wrote:
Generally recommend attaching patches as files ending in .patch (as
documented in docs/submissions.pod) for the sanity of the patch
monsters.
Well, since it's in the docs, I will withdraw the suggestion.
However, *I* am one of the
Allison Randal wrote:
James Keenan via RT wrote:
3. For future reference, submit bug reports to:
[EMAIL PROTECTED] I recommend beginning Subject line with:
[BUG]. And I recommend submitting patches as email attachment ending in
: .txt (because that seems to render best in browsers,
36 matches
Mail list logo
