OESF Portables Forum
Everything Else => Zaurus - Everything Development => Distros, Development, and Model Specific Forums => Archived Forums => User Request for Applications => Topic started by: Zismylaptop on May 22, 2005, 08:09:22 pm
-
I've used a 2002 (Jan 17) build of Perl 5.6.1 with great success with the Sharp rom. I don't remember where I found it. However, when installed under 3.5.3 (Opie) and called via "perl -v" it respoonds with "Illegal instruction" and returns to the bash prompt.
I remember once seeing a 5.8 arm.ipk that worked with an early version of opie, but it was relatively huge. But I don't know where I saw it, either.
Anybody have one? It shouldn't be hard to generate an ipk (if you know how to do these things) since it's natively unix.
Thanks.
-
The OE team has been struggeling against perl's obfuscated build system for long. Would you like to take a stab at finishing our .bb files?
-
Perhaps you can try the one from pdaxrom?
http://212.10.30.205/rc10/Zaurus-7x0-860/f....5_armv5tel.ipk (http://212.10.30.205/rc10/Zaurus-7x0-860/feed/perl_5.8.5_armv5tel.ipk)
and report if the libs are more or less compatible. (I believe pdaxrom ipks could work on oz as oz generally uses more up to date version and as they both use soft float point)
Perhaps the patches for the pdaxrom build system
http://pdaxrom.spy.org/patches-local/perl-5.8.5/ (http://pdaxrom.spy.org/patches-local/perl-5.8.5/)
are interesting for the oe team.
-
Perhaps you can try the one from pdaxrom?
http://212.10.30.205/rc10/Zaurus-7x0-860/f....5_armv5tel.ipk (http://212.10.30.205/rc10/Zaurus-7x0-860/feed/perl_5.8.5_armv5tel.ipk)
and report if the libs are more or less compatible. (I believe pdaxrom ipk could work on oe as oe generally uses more up to date version and as they both use soft float point)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81044\"][{POST_SNAPBACK}][/a][/div]
OE is a buildsystem. It can't use ipkgs, and deals with source. Using soft or hardfloat is a distribution decision, not something inherent to OE. Take a look at Familiar Linux, that's being built with OE but uses hardfloat.
-
The first part of my reply was for Zismylaptop who was looking for an ipk.
-
The first part of my reply was for Zismylaptop who was looking for an ipk.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81048\"][{POST_SNAPBACK}][/a][/div]
You said:
I believe pdaxrom ipk could work on oe
to which I replied stating that OE is a buildsystem. I was correcting a nonsense statement, so it doesn't matter to whom the original statement was directed.
-
ah ok I meant oz not oe. I have edited my post.
-
Thanks,
I downloaded the ipkg from pdxarom, but this is what I got.
root@kmcollie:/# ipkg install /media/card/3.5.3-ipks/perl_5.8.5_armv5tel.ipk
Clearing state_want and state_flag for pkg=perl (arch_priority=0 flag=16 want=2)
Nothing to be done
An error ocurred, return value: 4.
Collected errors: Cannot find package perl.
Check the spelling or perhaps run 'ipkg update'
root@kmcollie:/#
Are you all saying that the "Illegal instruction" is due to something about floating point? I know that the floating point behavior of the 5.6.1 perl I have been using on Sharp rom is quite abysmal.
-
pdaxrom compiles packages for armv5tel, these don't work on armv4 (collie).
-
When I installed gentoo on my poodle, perl and libperl compiled fine with an arm-gcc-3.3.4.
It did not compile with gcc-3.4.3.
Just to let you know
-
Mickey,
What is it that is hard about distributing perl? It seems to me there are three parts: compilation of the base package; choosing, gathering, and compiling the .pm's to distribute with it; and allowing the user to extend via CPAN. I doubt that the first step is the problem.
Although I've been a software developer for more years than many of our forum colleagues have been alive, I've had little to do with any unix systems and don't have a readily available linux box. Nevertheless, if I can help you, even to the extent of unsnarling obscure perl-isms for someone else to bit-bake, I'd be interested in trying.
Thanks
-
One of the problems we are facing is perl's tendency to hardcode paths during compilation: http://bugs.openembedded.org/show_bug.cgi?id=7 (http://bugs.openembedded.org/show_bug.cgi?id=7)