James Keenan via RT wrote:
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-precomp -pipe -I/usr/local/include
-pipe -fno-common -Wno-long-double -I./inc
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 $ MACOSX_DEPLOYMENT_TARGET=10.4
[parrot] 567 $ echo $MACOSX_DEPLOYMENT_TARGET
10.4
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?
>
How/where do I do that?
# New Ticket Created by James Keenan
# Please include the string: [perl #50314]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50314 >
As part of my exploration of t/harness (http://rt.perl.org/rt3/Ticket/
Display.html?id=
James Keenan via RT wrote on Sun, Jan 27, 2008 at 04:32:59PM PST:
> ...
> Determining what C compiler and linker to use...Compilation failed with
> '/usr/bin/gcc-3.3'
>
> Here's the output with -verbose-step=7 (inter::progs).
>
> Determining what C compiler and linker to use...
> ccflags: -fno-c
On Sunday 27 January 2008 09:36:27 Art Haas wrote:
> The test for the backtrace() function was failing due to the prototypes
> at the start of the test code differing for those listed in the header
> file. The patch below fixes things by removing the extra prototypes
> and basically copying the sa
# New Ticket Created by "Art Haas"
# Please include the string: [perl #50298]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50298 >
Hi.
The test for the backtrace() function was failing due to the prototypes
at the start
Thanks for taking the time to work on this patch.
Since the config/auto/backtrace.pm has not generated any configuration
or build failures for me on either Linux or Darwin, the most I would be
able to say is whether it does me any harm on either of those systems.
It did no harm on Linux, where it
I began by running configuration with tests. Specifically:
#!/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="$CX" --without-icu --without-gmp \
--test \
--configure_trace \
$@
... which is the way I
On Sun, Jan 27, 2008 at 10:33:20AM -0800, James Keenan via RT wrote:
> On Sun Jan 27 09:36:26 2008, [EMAIL PROTECTED] wrote:
> > Hi.
> >
> > The test for the backtrace() function was failing
>
>
> Could you post the failing test result?
>
> In particular, the output of 'prove -v t/steps/auto_b
On Sun Jan 27 09:36:26 2008, [EMAIL PROTECTED] wrote:
> Hi.
>
> The test for the backtrace() function was failing
Could you post the failing test result?
In particular, the output of 'prove -v t/steps/auto_backtrace*.t' would
be helpful.
I haven't seen any failures in these tests lately, so I
On Sun Jan 27 09:19:32 2008, [EMAIL PROTECTED] wrote:
>
> Allison: I have 3 different patches from you in this thread in the last
> day. Which one or which combination do you most want tried out?
Test the most recent one, darwin_full_dynamic_symbol_lookup.patch.
> (moi: ppc-darwin 10.4.11)
# New Ticket Created by James Keenan
# Please include the string: [perl #50302]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50302 >
As previously reported, I've begun looking at how to get us a better
smoke server setu
Patch applied to trunk in r25298.
Allison Randal via RT wrote:
If you're running some flavor of OS X, please test this patch.
Allison: I have 3 different patches from you in this thread in the last
day. Which one or which combination do you most want tried out?
(moi: ppc-darwin 10.4.11)
On Sun, 27 Jan 2008, Allison Randal wrote:
> Andy Dougherty via RT wrote:
> > I'd say rip it out and let someone who understands all the darwin-specific
> > behavior well worry about putting it in, *commenting it in the hints
> > file*, and maintaining it.
>
> Going back to a static build was th
The attached patch removes '-flat_namespace' and consistently uses
'-undefined dynamic_lookup'. It also restricts the changes to just the
darwin config hints file, which seems like a more appropriate place. It
resolves all the test failures related to undefined symbols on OS X.
(t/src/intlist.t is
17 matches
Mail list logo
