Below are my thoughts on this patch in it's current form.
I don't like the function of ld_libparrot_soname because it has the
soname mixed up with the linker flags. I'd rather see something like
ld_soflags and libparrot_soname (I don't have strong feelings about the
names).
Building a shared li
Hi,
I'm wondering, is there a PDD about Thread implementation in Parrot? I
searched the list archive, and found a lot of info. Dan even mentioned
writing a PDD on the subject, but I havent' been able to find it.
Thanks,
klaas-jan
Nick,
I'll try to take a look at all of this patch today. Quick questions -
why is:
+src/install_config.o [main]lib
being added to MANIFEST.generated?
-J
On Fri, Dec 23, 2005 at 06:25:44PM +, Nick Glencross wrote:
> Index: debian/libparrot.install
> ===
Nick Glencross wrote:
Guys,
Here's an updated version of the libparrot shared library patch.
Sorry, omitted one of the configure files!
I should mention that you probably want to remove
config/inter/libparrot.pm before ever reapplying the patch otherwise
you'll get the same content twice.
Guys,
Here's an updated version of the libparrot shared library patch. It
primarily adds back the functionality for SOVERSION. To do this I have
created two new compile flags which will usually be set in the platform
hints.
* ld_libparrot_soname: Supplied to ld to set the library version o
On 12/23/05, François PERRAD <[EMAIL PROTECTED]> wrote:
>
> OK with static on Win32 + gcc (MinGW).
>
> Shared on Win32, always the same linking problem with
> parrot_get_config_string()
> (see https://rt.perl.org/rt3/Ticket/Display.html?id=37303)
>
> g++ -shared -o blib\lib\libparrot.dll ...
>
>
This should fix the slowdown from the previous patch, while
maintaining correct output. It speeds things up by about 15% for me,
using JIT on x86.
--- mandelbrot.pir 2005-12-23 02:50:52.0 -0500
+++ mandelbrot-opt.pir 2005-12-23 03:15:53.0 -0500
@@ -68,15 +68,14 @@
Ci
At 12:51 22/12/2005 +, you wrote:
Guys,
I'd like to revive this patch which I posted a while back, but has needed
bringing up to date due to subsequent changes.
It has a few key intentions:
* Makes libparrot.so a 'first class citizen'
* Allows the installed version of parrot and its ut
The obvious way to implement Perl5 "local" bindings in Parrot would
be to:
1. Capture the old value in a temporary;
2. Use store_global to set the new value;
3. Execute the rest of the block; and
4. Do another store_global to reinstate the old value.
This has a serious flaw:
On Dec 23, 2005, at 0:17, peter baylies wrote:
Short version: uncomment lines 86-87, patch follows.
Thanks, applied - r10629.
leo
10 matches
Mail list logo
