James Keenan via RT wrote:
Nope.
[parrot] 521 $ ./myconfigure.sh
MACOSX_DEPLOYMENT TARGET is 10.3
There seems to be a missing underscore in "MACOSX_DEPLOYMENT TARGET",
but that's probably just your debug message.
Did you try 'export'? Configure spawns its own processes which may be
resett
On Mon, 28 Jan 2008, James Keenan via RT wrote:
> Here's the verbose output on the failing configuration step, inter::progs.
>
> First, with my usual settings:
>
> Determining what C compiler and linker to use...
> ccflags: -fno-common -no-cpp-precomp -pipe -I/usr/local/include -pipe
> -fno-co
Nope.
[parrot] 521 $ ./myconfigure.sh
MACOSX_DEPLOYMENT TARGET is 10.3
Parrot Version 0.5.2 Configure 2.0
Copyright (C) 2001-2008, The Perl Foundation.
Hello, I'm Configure. My job is to poke and prod your system to figure out
how to build Parrot. The process is completely automated, unless you
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #50360]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50360 >
Parrot's NCI callback subsystem design will not work (and cannot be
directly exten
Here's the verbose output on the failing configuration step, inter::progs.
First, with my usual settings:
Determining what C compiler and linker to use...
ccflags: -fno-common -no-cpp-precomp -pipe -I/usr/local/include -pipe
-fno-common -Wno-long-double
/usr/bin/gcc-3.3 -fno-common -no-cpp-pre
James Keenan via RT wrote:
I first tried setting the environmental variable, then using my startup
script in test mode:
$ echo $MACOSX_DEPLOYMENT_TARGET
10.3
#!/bin/sh
CC="/usr/bin/gcc-3.3"
CX="/usr/bin/g++-3.3"
/usr/local/bin/perl Configure.pl --cc="$CC" --cxx="$CX" --link="$CX" \
--ld="$
Patch applied to trunk in r25320.
On Mon Jan 28 00:30:51 2008, [EMAIL PROTECTED] wrote:
> James Keenan via RT wrote:
> >>
> > Okay, I figured out how to do that ... but no better results.
> >
> > [parrot] 566 $ MACOSX_DEPLOYMENT_TARGET=10.4
> [...]
> >
> > Setting the environmental variable apparently didn't stick.
>
> I can dup
On Sun Jan 27 21:48:22 2008, [EMAIL PROTECTED] wrote:
> Explicitly cast the argument of toupper in src/debug.c so that t/
> codingstd/check_toxxx.t passes.
Thanks, applied in r25314.
On Sun Jan 27 17:36:02 2008, [EMAIL PROTECTED] wrote:
> As part of my exploration of t/harness (http://rt.perl.org/rt3/Ticket/
> Display.html?id=50302), I had occasion to try the Test::Run variant.
> However, when I tried to install Test::Run today (no small feat, as
> it sits on a pile of no
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jan 28 14:00:03 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
On 26 Jan., 17:58, [EMAIL PROTECTED] (Larry Wall) wrote:
> Last night I got a message entitled: "yum: 1 Updates Available".
> Of course, that's probably just a Python programmer giving up on doing
> the right thing, but we see this sort of bletcherousness all the time.
>
> After a recent exchange o
# New Ticket Created by Michael Stephens
# Please include the string: [perl #50318]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50318 >
Explicitly cast the argument of toupper in src/debug.c so that t/
codingstd/check_t
On 28/01/2008, James Keenan via RT <[EMAIL PROTECTED]> wrote:
> On Sun Jan 27 17:14:11 2008, tiro wrote:
>
> >
> > Could you try setting MACOSX_DEPLOYMENT_TARGET to 10.4 to see if that
> > fixes the problem?
> >
> Okay, I figured out how to do that ... but no better results.
>
> [parrot] 566 $ MACO
James Keenan via RT wrote:
Okay, I figured out how to do that ... but no better results.
[parrot] 566 $ MACOSX_DEPLOYMENT_TARGET=10.4
[...]
Setting the environmental variable apparently didn't stick.
I can duplicate the failure when I use your startup script. First, try
setting the envir
15 matches
Mail list logo
