Interchange for SUSE also requires non-threaded perl.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I would like to package and maintain interchange for SUSE LINUX.
http://www.icdevgroup.org. It requires a non-threaded perl. The way I
have been doing it is compiling a non-threaded perl and putting it in
/usr/local/bin/. Installing from CPAN using
/usr/local/bin/perl -MCPAN -e 'install Bundle::Interchange'
Then creating the rpm for SUSE Linux. Interchange requires all these
modules. I would like to use the build service to do this. I requested a
build account in January of this year.
Do you think this is something the community would like?
Thanks,
- --
Boyd Gerber
Am Monday 08 May 2006 14:23 schrieb Boyd Lynn Gerber:
I would like to package and maintain interchange for SUSE LINUX. http://www.icdevgroup.org. It requires a non-threaded perl. The way I have been doing it is compiling a non-threaded perl and putting it in /usr/local/bin/. Installing from CPAN using
/usr/local/bin/perl -MCPAN -e 'install Bundle::Interchange'
Then creating the rpm for SUSE Linux. Interchange requires all these modules. I would like to use the build service to do this. I requested a build account in January of this year.
Sorry, the request get lost than somehow. I am ~2 weeks behind of the requests, but I have the hope to answer them in the next 2 days. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
On Tue, May 09, 2006 at 10:38:31AM +0200, Adrian Schröter wrote:
Am Monday 08 May 2006 14:23 schrieb Boyd Lynn Gerber:
I would like to package and maintain interchange for SUSE LINUX. http://www.icdevgroup.org. It requires a non-threaded perl. The way I have been doing it is compiling a non-threaded perl and putting it in /usr/local/bin/. Installing from CPAN using
/usr/local/bin/perl -MCPAN -e 'install Bundle::Interchange'
Then creating the rpm for SUSE Linux. Interchange requires all these modules. I would like to use the build service to do this. I requested a build account in January of this year.
This may be a dumb question, but if interchange doesn't use threads, why can't it work with a thread enabled perl? (Thread enabled means that you *can* use threads, it doesn't mean that you have to). Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
On Tue, May 09, 2006 at 11:38:37AM +0200, Michael Schroeder wrote:
This may be a dumb question, but if interchange doesn't use threads, why can't it work with a thread enabled perl? (Thread enabled means that you *can* use threads, it doesn't mean that you have to).
Well, maybe they use code that is not thread safe but use modules that make use of threads if available. Actually I don't know if this really is the problem but one possible cause. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, May 09, 2006 at 11:38:37AM +0200, Michael Schroeder wrote:
This may be a dumb question, but if interchange doesn't use threads, why can't it work with a thread enabled perl? (Thread enabled means that you *can* use threads, it doesn't mean that you have to).
Well, maybe they use code that is not thread safe but use modules that make use of threads if available. Actually I don't know if this really is the problem but one possible cause.
This is correct. I still find problems with perl-threads. It has gotten
a lot better. Some of the modules in interchange or used by interchange
seem to not be thread safe. Also threads with perl seem to be OS
dependent. Some OS's the perl threads are still experimental IMHO.
Thanks,
- --
Boyd Gerber
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, May 09, 2006 at 10:38:31AM +0200, Adrian Schröter wrote:
Am Monday 08 May 2006 14:23 schrieb Boyd Lynn Gerber:
I would like to package and maintain interchange for SUSE LINUX. http://www.icdevgroup.org. It requires a non-threaded perl. The way I have been doing it is compiling a non-threaded perl and putting it in /usr/local/bin/. Installing from CPAN using
/usr/local/bin/perl -MCPAN -e 'install Bundle::Interchange'
Then creating the rpm for SUSE Linux. Interchange requires all these modules. I would like to use the build service to do this. I requested a build account in January of this year.
This may be a dumb question, but if interchange doesn't use threads, why can't it work with a thread enabled perl? (Thread enabled means that you *can* use threads, it doesn't mean that you have to).
The problem is that when a thread perl is used the system will hang and
or become real slow. Some modules do have interaction problems. See...
http://www.icdevgroup.org/pipermail/interchange-users/2005-June/043272.html
If real care is taken one can use a threaded perl. I have just had too
many problems all solved by using a non-thread perl.
Thanks,
- --
Boyd Gerber
participants (4)
-
Adrian Schröter -
Boyd Lynn Gerber -
Michael Schroeder -
Robert Schiele