Re: Perl for arm buildroot target

Replies are listed 'Best First'.
Re^2: Perl for arm buildroot target by wol (Hermit) on May 12, 2009 at 11:22 UTC
I wondered too, but the nodes have different writing styles (not to mention formatting styles) so they do at least come from two different people. Of course, it could be two different different people from the same team working on that problem... I could hypothesise all day. Unfortunately, that's not the same as being able to answer the question(s). -- use JAPH; print JAPH::asString();	[reply]
Re^2: Perl for arm buildroot target by cbanker (Beadle) on May 12, 2009 at 17:26 UTC
Not at all related to the other post that you pointed out, but thanks for making me aware of that. My problem is fairly similar, but slightly different, as I do not have an SSH connection to the board. I create an image using buildroot and load that to the board. I need to either create a buildroot makefile to run as part of the buildroot process, find pre-compiled binaries, or perform a cross-compile to make binaries that I can add into the filesystem that is written to the image. The tip about the Nokia port seems like it might be a good lead, so I'm going to look into that. However, if anyone has other suggestions, or can provide further information or links for the Nokia perl port, that would be great. Update: I looked into the option of using the perl port done by Nokia: http://opensource.nokia.com/projects/symbian-perl/index.html. From what I can tell Nokia only provides SIS packages, which don't do me much good.	[reply]
Re^3: Perl for arm buildroot target by afoken (Chancellor) on May 14, 2009 at 14:01 UTC
You are right, you need a full-featured Perl build to use DBI. As far as I understand the Perl build process, it must run on the target system, which makes cross-compiling a littler bit harder. If you had a complete native toolchain for the target system, you could compile perl there. A telnet or ssh connection to the target would be helpful. Do you know Cross/README? It seems that comes close to your problem. Generating a proper config file is the job of the `Configure` script, but you can also write it manually. I would try to run `Configure` interactively on the target system, using a telnet or ssh connection, then copy the generated config file back to the development system. From there, building Perl should be relatively simple. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l] [select]
Re^4: Perl for arm buildroot target by cbanker (Beadle) on May 14, 2009 at 19:51 UTC
Thanks for the tips about using the Cross folder in the perl distribution. I had looked at that before, but was running into errors when compiling it, so I had given up on using that option. However, I'm guessing those errors were due to the fact that I was using the default configuration, so I'm going to give it another try. I'm working on running `Configure` on the target right now, however I need to get my very minimalistic target system up to the point where it can actually run `Configure`. The difficulty with this system is that nearly everything is cross-compiled, so there is very little in the way of standard utilities on the target. Hopefully I can get this to work out. Going back to the buildroot method I was trying: Does anyone know why building full perl as part of the buildroot make is such a problem, even though I'm able to successfully build microperl that way? Is it likely that there are inherent issues with building full perl that way or might it just be that I still have problems with my makefile for the full perl buildroot make?	[reply] [d/l] [select]