Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[perl #41500] [TODO] config - lib directory needs to be set appropriately for 32/64 bit archs

3 views
Skip to first unread message

Paul Cochrane

unread,
Feb 13, 2007, 11:42:29 AM2/13/07
to bugs-bi...@rt.perl.org
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #41500]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41500 >


In config/init/defaults.pm the lib install path needs to be set
correctly for 32 and 64 bit architecture systems.

James Keenan via RT

unread,
Sep 4, 2007, 9:13:58 PM9/4/07
to perl6-i...@perl.org
On Tue Feb 13 08:42:29 2007, ptc wrote:
> In config/init/defaults.pm the lib install path needs to be set
> correctly for 32 and 64 bit architecture systems.


Paul: This is one of those tickets that you created on the basis of an
inline comment (which was perhaps originally written by leo). Is it
still valid or can the ticket be closed?

Thank you very much.

kid51

Joshua Isom

unread,
Sep 5, 2007, 2:48:31 AM9/5/07
to parrotbug...@parrotcode.org, Perl 6 Internals
As far as I know the code in question would primarily apply to Linux on
amd64. It may also apply to other systems on amd64, but I know that
particular directory structure is used with Linux. FreeBSD is not
affected(but then again, I never have gotten a 32 bit working build).

Paul Cochrane

unread,
Sep 5, 2007, 3:56:59 AM9/5/07
to parrotbug...@parrotcode.org, st...@silug.org
On 05/09/07, James Keenan via RT <parrotbug...@parrotcode.org> wrote:
> On Tue Feb 13 08:42:29 2007, ptc wrote:
> > In config/init/defaults.pm the lib install path needs to be set
> > correctly for 32 and 64 bit architecture systems.
>
>
> Paul: This is one of those tickets that you created on the basis of an
> inline comment (which was perhaps originally written by leo). Is it
> still valid or can the ticket be closed?

kid51,

To be totally honest, I don't know. I'm not testing on 64 bit
platforms atm, so I can't give it a go. It's one of those instances
where we have to wait for someone working on a 64 bit platform (amd64,
say) tells us if things are working properly or not. Oh for a
compiler farm like we used to have on sf.net... My guess as to the
status of this ticket is that it is effectively stalled, but not
closed.

ptc

Timothy S. Nelson

unread,
Sep 16, 2009, 6:01:57 AM9/16/09
to James Keenan via RT, parro...@lists.parrot.org
On Tue, 15 Sep 2009, James Keenan via RT wrote:

> On Sun Jul 19 12:07:24 2009, jk...@verizon.net wrote:
>>
>> It appears that this ticket effectively stalled two years ago for lack
>> of testers on 64-bit platforms. However I believe that recently we have
>> had a big increase in the amount of testing going on on AMD64 and even
>> Win64. The fact that we haven't seen a lot of Trac tickets about
>> incorrect 'lib install paths' (not exactly sure what that means)
>> suggests that whatever we're doing now is sufficient and that this
>> ticket can be closed.
>>
>> Could anyone who is familiar with those platforms tell us if we are
>> doing the right thing with respect to installation paths?
>>
>
> Can any of our developers working on 64-bit platforms help out here?

Hopefully within the next month I'll be trying to build a new Parrot
RPM. But I'm having one of those months at the moment -- sorry.

:)


---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: way...@wayland.id.au | I am |
---------------------------------------------------------------------

----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----

James Keenan via RT

unread,
Sep 25, 2009, 6:50:31 PM9/25/09
to parro...@lists.parrot.org, perl6-i...@perl.org
This ticket has been open for more than two-and-a-half years -- solely
on the basis of an ancient inline comment. In that time no one has
produced any evidence that we are doing the wrong thing. Given how many
of our developers are currently working on AMD64, I would have expected
that by now some evidence of doing the wrong thing would have emerged.

I am therefore taking this ticket, removing the inline comment from
config/init/defaults.pm and resolving the ticket. Wayland, if you get
around to testing the install paths on 64-bit and we're doing the wrong
thing, please open up a Trac ticket with full details.

0 new messages