On Tue, 22 Sep 2009, Nicholas Clark wrote:
> On Tue, Sep 22, 2009 at 02:22:17PM -0400, Andy Dougherty wrote:
> > On Tue, 22 Sep 2009, Will Coleda via RT wrote:
> >
> > > On Tue Jul 08 20:56:02 2008, s1n wrote:
> > > > When trying to use the --optimize flag, bu
( ' ', ccflags => "-DDISABLE_GC_DEBUG=1" );
if ( $optimize eq "1" ) {
# use perl5's value
However, in principle, the various __nonnull__ attributes mean that gcc is
still free to optimize away at least some of the ASSERT checks.
--
Andy Dougherty dough...@lafayette.edu
, you mean here, but that's ok.
> 2. Allow all keys to be given at the Configure.pl cmdline as in perl5.
>Append (Apply after hints), Undefine and Define.
See the related discussion in [perl #42412]. (I've updated RT with the
relevant link.)
In any case, I won't have any time to do anything parrot-related for at
least the next several weeks, so I'm afraid I can't be of further help
here.
--
Andy Dougherty dough...@lafayette.edu
her or not the perl used to run
Configure.pl has long double support or not. Hence I conclude that having
a perl compiled with long double support isn't necessary.
It does look like there's a JIT bug somewhere -- probably, Configure.pl
should simply refuse to try JIT if you insist on building with
non-standard data types, but that's a different issue.
--
Andy Dougherty dough...@lafayette.edu
s) but leaving the -D40 branch as a possible
debugging tool.
--
Andy Dougherty dough...@lafayette.edu
ignbit() (which, alas, perl 5 doesn't probe for).
Some of these functions might only be available under certain compiler
options or with certain extra libraries, depending on how a particular
system attempts to adhere to different standards, but it's probably worth
trying them.
--
Andy Dougherty dough...@lafayette.edu
On Wed, 31 Dec 2008, chromatic wrote:
> On Wednesday 31 December 2008 12:26:07 Andy Dougherty wrote:
>
> > This is not a hypothetical what-if situation. I have lost many hours to
> > just this situation. See my long example in ticket RT #50684. To save
> > everyone fr
significant way. I was
just trying to help keep the entry barrier low for others.
But I don't really care very much, so I'll stop now.
--
Andy Dougherty [EMAIL PROTECTED]
ot-latest.tar.gz
cat > patch-2.12 < test.log 2>&1
cd ..
mv parrot parrot-2.12
gzip -d -c Storable-2.18.tar.gz | tar -xf -
cd Storable-2.18
$perl Makefile.PL
make
make install
cd ..
# Build using Storable 2.18
gzip -d -c parrot-latest.tar.gz | tar -xf -
cd parrot
$perl
On Thu, 13 Nov 2008, chromatic wrote:
> On Monday 03 November 2008 09:38:11 Andy Dougherty wrote:
>
> > > 3. 1 of the tests appears to fail depending on how the OS initial-
> > > cases 'Inf'. Again, could this be addressed in a hints file?
> >
>
On Sat, 8 Nov 2008, chromatic wrote:
> On Monday 03 November 2008 09:38:11 Andy Dougherty wrote:
>
> I wonder if this patch fixes things. Certainly it does no harm on my box.
> Parrot_signbit() already exists in the platform files, so we might as well
> use it.
> --
on getting me accounts on them
> and, if that comes through, I'll be able to post Configure.pl and make
> output.
Even more immediately useful would be the 'myconfig' info for each
configuration. I designed the file to be useful in precisely this sort of
situation.
--
Andy Dougherty [EMAIL PROTECTED]
he same and what's different.
> 3. 1 of the tests appears to fail depending on how the OS initial-
> cases 'Inf'. Again, could this be addressed in a hints file?
This too is a long-standing problem: See [perl #19183]. It stalled
pending a decision on whether or not parrot should try to enforce a single
spelling of 'Inf' (and 'Nan', etc.) or whether the tests should patch over
the issue.
--
Andy Dougherty [EMAIL PROTECTED]
mpiler options were given? All this information, and more, is given in
the 'myconfig' file. Attaching that to the problem report would likely be
useful.
Also, running the core tests might help pinpoint the problem.
--
Andy Dougherty [EMAIL PROTECTED]
ot (and also with parrot -G to turn off garbage collection) and
see what's the smallest or simplest failing test case you can find. They
might be better candidates for debugging.
--
Andy Dougherty [EMAIL PROTECTED]
On Sat, 25 Oct 2008, Michael P. Soulier wrote:
> On 15/10/08 Andy Dougherty said:
>
> > > No file by that name on the box anywhere.
> >
> > Are you *sure*? I don't know exactly what name you searched for, nor how
> > you searched for it, but this is jus
On Tue, 21 Oct 2008, Andrew Whitworth wrote:
> On Tue, Oct 21, 2008 at 9:28 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Mon, 20 Oct 2008, Andrew Whitworth via RT wrote:
> >
> >> On Fri Mar 31 13:29:46 2006, leo wrote:
> >> > That is, our conf
rs who can double-check this and see
> if we still have a problem here?
Yes, we still have exactly the same problem. Anyone can check this by
editing their perl Config settings and seeing that they get passed through
unquestioningly to parrot.
--
Andy Dougherty [EMAIL PROTECTED]
get for the following commands:
nm src/embed.o | grep 'Parrot_new$'
nm blib/lib/libparrot.so | grep 'Parrot_new$'
--
Andy Dougherty [EMAIL PROTECTED]
ernal'
> collect2: ld returned 1 exit status
> make: *** [miniparrot] Error 1
>
> I found one bug online like this, where the fix was not using tcsh,
> but I don't use tcsh.
Do you have a link for that bug report? I vaguely recall something like
that where the tcsh was a red herring -- it was really an environment
variable setting -- but I don't recall any more details offhand.
--
Andy Dougherty [EMAIL PROTECTED]
tly requires: 2.13. However, if you
only have 2.12 and go to CPAN to upgrade, you'll end up with 2.18, which
is what chromatic was referring to.
--
Andy Dougherty [EMAIL PROTECTED]
rable 2.12 instead of 2.13, and then
building with Storable 2.12, also seems to work. That is, there are no
significant differences between the generated files.
--
Andy Dougherty [EMAIL PROTECTED]
ance to investigate further this
> > evening, if somebody hasn't beaten me to it.
>
> Yes, that's generated code, it's part of the initialization of MULTIs
> declared in a PMC. I was hoping to avoid all those C strings. But, try
> r31879.
Yes, that works fine.
Thanks,
--
Andy Dougherty [EMAIL PROTECTED]
ould definitely use it,
but I wouldn't want anyone else to be stuck implementing and maintaining
it just for my occasional use.
--
Andy Dougherty [EMAIL PROTECTED]
t
doesn't. However, perl5's Configure does (at least for Unix systems), so
you could just use it's results.
--
Andy Dougherty [EMAIL PROTECTED]
rw-r--r-- 1 jimk jimk 1330 Sep 10 19:58 test_26632.c
> -rw-r--r-- 1 jimk jimk 0 Sep 10 19:58 test_26632.out
> -rwxr-xr-x 1 jimk jimk 18148 Sep 10 19:58 test_26632
--
Andy Dougherty [EMAIL PROTECTED]
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
$conf->data->set(
aio=> 'define',
HAS_AIO=> 1,
-D_SIGRTMIN => $1,
-D_SIGRTMAX => $2,
);
}
else {
--
Andy Dougherty [EMAIL PROTECTED]
h
forward.
As you correctly observe, no one has actually done anything about it yet.
That doesn't mean it's not worth doing, however.
I'd say it should simply stay as an open ticket.
--
Andy Dougherty [EMAIL PROTECTED]
re/man/man2/aio_return.2
> /usr/share/man/man2/aio_suspend.2
> /usr/share/man/man2/aio_write.2
>
> ... 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 wron
conf, $libs, $verbose) = @_;
-$conf->data->set( libs => $libs );
+$conf->data->set(
+aio=> undef,
+HAS_AIO=> 0,
+);
+$conf->data->set( libs => $libs ); # Restore old values
print " (no) " if $verbose;
$self->set_result('no');
}
--
Andy Dougherty [EMAIL PROTECTED]
symlinks aren't available on
Unix, it falls back to a plain 'ln'. On Win32 versions of perl, lns is
usually defined as 'copy'.
So the short answer is that, at the moment, without additional
Configure.pl work, you can't assume $Config{lns} can be used to make
symbolic links for directories.
--
Andy Dougherty [EMAIL PROTECTED]
ls back on
using the incorrect value of 'cc' that perl5 was built with.
--
Andy Dougherty [EMAIL PROTECTED]
stitution. We used the language's
built-in conditional and flow control syntax to express complex ideas.
--
Andy Dougherty [EMAIL PROTECTED]
is you have different environment
variables set under tcsh and bash. This error looks like the one we see
when there is an already-installed libparrot.so somewhere that conflicts
with the the one you're trying to build. (You don't show the compiler
command line that generated the error, so this is only a guess.)
--
Andy Dougherty [EMAIL PROTECTED]
argument to the build and run commands.
But for now, this at least should work, which is better than it was!
Thanks,
--
Andy Dougherty [EMAIL PROTECTED]
time
inter::progs -- Choose compiler (by Configure.pl command-line option)
-- accept hints file settings, whether they apply to
this compiler or not.
See the discussion in [perl #41195] for some more background and
examples.
--
Andy Dougherty [EMAIL PROTECTED]
;
-A eval:symbol=value define symbol to be eval of value
-A prepend:symbol=value prepend value to symbol
-A undef:symbol define symbol to be 'undef'
-A undef:symbol= define symbol to be ''
e.g.: -A prepen
7;m not sure what there is to flush out. There's one line in the hints
file that has $ccflags = . . . . That's the line that's wrong. It
obviously doesn't honor any command-line flags.
--
Andy Dougherty [EMAIL PROTECTED]
but that configure is ignoring the --ccflags argument.
Right. The problem is still exactly the same -- the hints file is still
unconditionally overwriting ccflags. Since that hasn't changed, the
problem is still there.
--
Andy Dougherty [EMAIL PROTECTED]
ontain their actual
> implementation
>
> I don't know whether we expect enough usage of Parrot in mathemetical circles
> to be worthwhile adding one of these implementions to our version of sprintf.
Perl5 certainly gets used in situations where such issues are relevant.
Every tim
On Wed, 30 Jul 2008, chromatic wrote:
> On Wednesday 30 July 2008 11:20:33 Andy Dougherty wrote:
>
> > Ahh -- it's just an octal/decimal mix-up. Here's the patch:
> >
> > --- parrot-current/t/steps/auto_icu-01.t2008-07-30 13:45:19.0
> > -04
le to make testing directory";
-mkpath($expected_include_dir, 0, 755)
+mkpath($expected_include_dir, 0, 0755)
or croak "Unable to make second-level testing directory";
($icuheaders, $without) =
$step->_handle_icuheaders($conf, qq{$expected_dir\n
n/alpha/include: Permission denied
> >
>
> I don't recall writing any tests which call for such strange
> permissions, but I will nonetheless look into this problem.
I suspect it's the icu tests. Or at least a quick 'grep' for 'alpha' and
'include' suggest it's the icu tests.
--
Andy Dougherty [EMAIL PROTECTED]
al) line
339, at lib/Parrot/Configure.pm line 509
# Looks like you planned 44 tests but only ran 16.
# Looks like your test died just after 16.
dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 17-44
Failed 28/44 tests, 36.36% okay
--
Andy Dougherty [EMAIL PROTECTED]
truly a SPARC-specific issue.
So another reasonable possibility is to just delete that whole section of
code and make no sparc-specific changes to CFLAGS.
--
Andy Dougherty [EMAIL PROTECTED]
x27;) || $intval;
$conf->data->set(
iv => $intval,
More generally, I was just making my usual rant that prior to extensive
refactoring or testing of any file, it makes sense to consider whether the
existing behavior is even worth refactoring or testing. (Specifically,
I'm thinking about the auto/pack.pm stuff. This opcode_t stuff is more
subtle, but it came up recently in another context, so I thought I'd
mention it.)
--
Andy Dougherty [EMAIL PROTECTED]
ails,
but, parrot shouldn't assume that all linkers are similarly insensitive.
--
Andy Dougherty [EMAIL PROTECTED]
specifically 0 if successful, and something else
otherwise. (What that "something" else actually is seems to be
defined differently by different vendors, alas. OpenBSD and Solaris
return errno. Linux/glibc returns -1.)
--
Andy Dougherty [EMAIL PROTECTED]
On Mon, 14 Jul 2008, Andy Dougherty wrote:
> On Mon, 14 Jul 2008, James Keenan via RT wrote:
> > 3. Are there any other configuration steps which are no longer needed?
>
> Well, I proposed eliminating the attributes and warnings tests, but I was
> overruled on that.
s all these platforms, I think the ticket is resolved. If
> not, maybe we need to break this into more-specific sub-tickets for each
> failing platform.
It still fails in the identical way on Solaris 8/SPARC with gcc.
--
Andy Dougherty [EMAIL PROTECTED]
list [perl #56484] that
brought up a closely-related issue.
> 3. Are there any other configuration steps which are no longer needed?
Well, I proposed eliminating the attributes and warnings tests, but I was
overruled on that. Other than those, nothing occurs to me off the top of
my head.
--
Andy Dougherty [EMAIL PROTECTED]
L) != sizeof(void *).
Thus while it's probably generally true that sizeof(opcode_t) ==
sizeof(INTVAL), it's not enforced at the Configure.pl level.
In sort, it certinaly shouldn't be hard to include INTVALSIZE in the
PackFile header, but you can also probably "temporari
be repeated.
To give some sense of scale: On my aging-but-busy Solaris 8/SPARC system,
the configure tests take about 15 minutes to run, and account for about
1/4 of the total run time for 'make test'.
--
Andy Dougherty [EMAIL PROTECTED]
e error went away if you padded the string
structure with an extra element, so it does indeed smell like an alignment
assumption somewhere. My first guess was that calculations involving
sizeof(Buffer) were now questionable, but that was just a guess.
--
Andy Dougherty [EMAIL PROTECTED]
worry was
more related to memory constructs that are not explicit structures, but
that are managed "by hand" (e.g. the refcount in src/resources.c).
--
Andy Dougherty [EMAIL PROTECTED]
Dept. of Physics
Lafayette College, Easton PA 18042
ery long time. Looking back at my (very incomplete) archives, the last
success I had with this configuration was on Dec 19, 2002. There is a
very old ticket [perl #18189] on this issue too. There are some remarks
in there that might still be relevant.
(Odd. That ticket seems to be marked resolved, though I thought by
replying to it I would have reopened it.)
--
Andy Dougherty [EMAIL PROTECTED]
command
line option. Again, I don't know why, and it seems backwards to me,
but I'm reluctant to suggest changing it in case it was deliberate.
More generally, the default MAKE setting ought not to be recursive. I
really don't know why that variable is called MAKE instead of something
like MAKE_C. Using MAKE_C would eliminate the recursive issue without
the "ugly hack".
--
Andy Dougherty [EMAIL PROTECTED]
On Sat, 14 Jun 2008, chromatic via RT wrote:
> On Tuesday 07 August 2007 10:11:20 Andy Dougherty wrote:
>
> > This next patch does a little more cleanup on the attributes checking. I
> > revised config/auto/attributes.pm to use the existing Configure routines
> > cc_bu
ussion can be found here
(and the surrounding thread):
http://www.nntp.perl.org/group/perl.perl6.internals/2006/03/msg33340.html
--
Andy Dougherty [EMAIL PROTECTED]
ine this? Could this be
> converted into a coding standards test?
On a Unix-like system, you can use nm(1) to look at blib/lib/libparrot.a.
(The appropriate options are system-dependent, but 'nm -p' is usually a
good bet.)
--
Andy Dougherty [EMAIL PROTECTED]
On Fri, 6 Jun 2008, Steve Peters wrote:
> On Fri, Jun 6, 2008 at 8:12 AM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Thu, 5 Jun 2008, Will Coleda via RT wrote:
> >
> >> If the patch is applied, is this ticket safe to close now?
> >
> > No. It&#
On Thu, 5 Jun 2008, Will Coleda via RT wrote:
> On Tue May 15 14:54:01 2007, [EMAIL PROTECTED] wrote:
> > On Wednesday 09 May 2007 07:21:44 Andy Dougherty wrote:
> >
> > > [appending to an old ticket, since if anyone wants to ever get this
> > > working again, th
On Thu, 5 Jun 2008, Will Coleda via RT wrote:
> On Tue Jan 15 20:08:22 2008, [EMAIL PROTECTED] wrote:
> > Patches applied to trunk in r24898.
>
> Can we close this ticket if the patches are applied?
Yes, this one can be closed.
--
Andy Dougherty [EMAIL PROTECTED]
en useless for a couple of years now)
Alas, I suspect it probably doesn't generally work. I seem to recall that
t/harness doesn't pass through unrecognized arguments, so something
sensible-looking like
make test PARROT_ARGS='--runcore=gcdebug'
won't actuall
do when presented with the code
int *a, i;
a = NULL;
i = *a;
The actual result you get will depend on the compiler, the optimization
level, and the runtime environment.
--
Andy Dougherty [EMAIL PROTECTED]
On Mon, 28 Apr 2008, chromatic wrote:
> On Monday 28 April 2008 10:24:37 Andy Dougherty wrote:
>
> > On Sun, 27 Apr 2008, chromatic wrote:
>
> > > /* Parrot Object - base class for all others */
> > > typedef struct pobj_t {
> > > +
ow at the earliest that
I can report anything back. (Longer, if manual intervention is required
to fix unrelated errors.)
--
Andy Dougherty [EMAIL PROTECTED]
On Thu, 24 Apr 2008, Andy Dougherty wrote:
> On Wed, 23 Apr 2008, Andy Dougherty wrote:
>
> > 2. There are some casting and type-punning warnings that have, as their
> > ultimate cause, the STACK_DATAP() macro. Getting rid of the
> > type-punning warning gives rise to
On Wed, 23 Apr 2008, Andy Dougherty wrote:
> 2. There are some casting and type-punning warnings that have, as their
> ultimate cause, the STACK_DATAP() macro. Getting rid of the
> type-punning warning gives rise to a cast alignment warning.
>
> Looking up a level, the only uses
arting to
develop the configure step?
This seems to me more of the level of a coding standard warning, not a
fatal error.
--
Andy Dougherty [EMAIL PROTECTED]
v
(According to the notes in perl5's hints/linux.sh, Red Hat uses a similar
naming convention.)
--
Andy Dougherty [EMAIL PROTECTED]
dumps will ensue.
--
Andy Dougherty [EMAIL PROTECTED]
perl Configure.pl --optimize='-xtarget=native'
will allow the compiler to choose the optimal alignment and it might
improve performance measurably. (Or it could be that this doesn't make
much of a difference anymore, the way it used to with older SPARCs.)
It may also be w
mimic elsewhere. Some time ago I also posted step by step
instructions for simulating this on any other system.
Some things are Solaris-specific[*], however, so Solaris testing is indeed
a good idea.
[*] Or, more commonly, non-GNU specific.
--
Andy Dougherty [EMAIL PROTECTED]
6914. Though I have no idea why r26916
> fixed it and r26914 didn't.
Well, adding those tests works around the design oddity, but I wouldn't
really call it "fixed".
--
Andy Dougherty [EMAIL PROTECTED]
On Wed, 9 Apr 2008, Will Coleda via RT wrote:
> On Fri Apr 04 22:28:31 2008, [EMAIL PROTECTED] wrote:
> > On Thursday 03 April 2008 11:22:16 Andy Dougherty wrote:
> >
> > > parrot-andy/compilers/imcc/optimizer.c ---
> > > parrot-svn/compilers/imcc/optimizer.c
nk all
the *BSD collections are reasonably similar.
If macports is indeed similar to FreeBSD ports, then this is good step
forward. If it is not, however, you might want to reserve the name
auto:ports for the FreeBSD-style ports collection.
--
Andy Dougherty [EMAIL PROTECTED]
On Wed, 2 Apr 2008, chromatic wrote:
> On Wednesday 02 April 2008 06:26:40 Andy Dougherty wrote:
>
> > This very minimal patch at leasts gives a brief warning about the issue.
>
> > +# Parrot can't necessarily handle a pre-existing installed shared
> > +
a while back, so we ought to rearrange the linker flags for pbc_to_exe
> in the same way.
Yes. Well spotted. I had leaped ahead to the next problem -- the
already-installed-shared-library -- but you are quite right. This
more immediate problem also needs solving. Your patch ought to do it.
shared parrot library may conflict " .
+ "with your previously-installed $old_version\n");
+}
+
if (
$conf->options->get('ask')
&&
--
Andy Dougherty [EMAIL PROTECTED]
not appear on a Centos or a MacOsX System.
My guess is that those systems do not have a previously installed
libparrot somewhere where the linker can find it.
--
Andy Dougherty [EMAIL PROTECTED]
earlier
copy of libparrot in /usr/local/lib might be getting picked up. I don't
see the command line used to build parrot itself, but I think that the
flags are in a different order so ./blib/lib comes earlier.
--
Andy Dougherty [EMAIL PROTECTED]
lly invoked from the root directory, then
../lib and ../../lib are looking outside of the parrot source. This is
wrong, since there is no guarantee that stuff stored in ../../lib is even
remotely suitable for parrot, or indeed for any other use.
--
Andy Dougherty [EMAIL PROTECTED]
X */
#include
int main(int argc, char *argv[])
{
+SHA256_CTX c; /* Only available in 0.9.8 and later */
unsigned long dummy = ERR_get_error();
printf ("%s\n", OPENSSL_VERSION_TEXT);
--
Andy Dougherty [EMAIL PROTECTED]
ave parts of the "crypto" support conditionally included,
depending on whether or not the user has that specific functionality
available.
--
Andy Dougherty [EMAIL PROTECTED]
On Thu, 13 Mar 2008, chromatic via RT wrote:
> On Thursday 13 March 2008 09:14:07 Andy Dougherty wrote:
>
> > On Thu, 13 Mar 2008, Nicholas Clark via RT wrote:
>
> > > Specifically, I am suspecting that if
> > >
> > > offsetof(struct
there is no actual "Buffer" inside a string
anymore. To be fair, though, there's a *lot* more going on in parrot's
memory management that I just don't understand, and I have been unable
to pinpoint a specific assignment that is in error.
--
Andy Dougherty [EMAIL PROTECTED]
On Wed, 12 Mar 2008, chromatic wrote:
> On Wednesday 12 March 2008 15:07:08 Andy Lester wrote:
>
> > On Mar 12, 2008, at 4:50 PM, Andy Dougherty via RT wrote:
> > > The problem is twofold:
> >
> > I'm not sure what you're saying is a p
On Wed, 12 Mar 2008, Andy Lester wrote:
>
> On Mar 12, 2008, at 2:33 PM, Andy Dougherty via RT wrote:
>
> > +#ifdef HASATTRIBUTE_NONNULL_AND_I_REALLY_WANT_TO_USE_IT
> > # define __attribute__nonnull__(a) __attribute__((__nonnull__(a)))
> > #endif
>
ase where the annotation was correct -- pool wasn't supposed
to be NULL -- but it made it harder to debug.
--
Andy Dougherty [EMAIL PROTECTED]
sponse to [perl #41168]:
To be blunt, I am more interested at the moment in whether it's
trying to do something sensible than whether or not its actual current
behavior is being tested. Testing the existing behavior assumes that
the existing behavior is what the program s
planned 9 tests but ran 2.
t/steps/auto_perldoc-02.t (Wstat: 256 Tests: 22 Failed: 1)
Failed test: 3
Non-zero exit status: 1
Files=261, Tests=2680, 448 wallclock secs (12.22 usr 3.23 sys + 349.94 cusr
57.21 csys = 422.60 CPU)
Result: FAIL
Pre-configuration tests did not complete successfully; Configure.pl will not
continue. at lib/Parrot/Configure/Options/Test.pm line 167.
--
Andy Dougherty [EMAIL PROTECTED]
configure-test.out.bz2
Description: Output of perl Configure.pl --test
elevant code is mostly in perl.c and
util.c, along with various Configure tests. There are additional
vms-specific implementations in vms/vms.c. It's been a long time since I
looked at any of it. I just remember it being complicated.)
--
Andy Dougherty [EMAIL PROTECTED]
On Mon, 18 Feb 2008, chromatic wrote:
> On Monday 18 February 2008 06:43:22 Andy Dougherty wrote:
>
> > The problem here looks relatively simple: The symbol _Parrot_conv_i2_i
> > is defined in two places: myops_ops.o and
> > /usr/local/lib/libparrot.dylib(core_ops.o)
On Mon, 18 Feb 2008, James E Keenan wrote:
> Andy Dougherty wrote:
>
> > The problem here looks relatively simple: The symbol _Parrot_conv_i2_i
> > is defined in two places: myops_ops.o and
> > /usr/local/lib/libparrot.dylib(core_ops.o)
> > That '/usr/loca
present, and why I think attempts to make it easy to install (e.g via yum,
macports, rpm, apt-get, etc.) are not a good idea at this time.
--
Andy Dougherty [EMAIL PROTECTED]
onfigure.pl --test and checked to see whether any files were
> created under /tmp during the past 5 minutes. None were created.
>
> There may, of course, be files run during make test that I didn't write
> that have these problems. But I think I've caught my ca
st check it in
the hints file and die with an informative error message.
--
Andy Dougherty [EMAIL PROTECTED]
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.
>
>
1 - 100 of 644 matches
Mail list logo
