in reply to Re: Can I install CPAN itself on busybox?
in thread Can I install CPAN itself on busybox?
I've gotten closer to my goal though:
which now gives thisvi /etc/opkg/distfeeds.conf #remove the comments opkg update opkg upgrade perl opkg install perlbase-cpan
so I will have another go with makemaker after all...root@Omega-C50F:/usr/lib/perl5/5.22# perl -MCPAN -e shell Can't locate ExtUtils/MakeMaker/version/vpp.pm in @INC (you may need t +o install the ExtUtils::MakeMaker::version::vpp module) (@INC contain +s: /usr/lib/perl5/5.24 /usr/lib/perl5/5.22) at (eval 6) line 2. BEGIN failed--compilation aborted at (eval 6) line 2. Compilation failed in require at /usr/lib/perl5/5.24/ExtUtils/MakeMake +r.pm line 9. BEGIN failed--compilation aborted at /usr/lib/perl5/5.24/ExtUtils/Make +Maker.pm line 9. Compilation failed in require at /usr/lib/perl5/5.24/CPAN.pm line 43. BEGIN failed--compilation aborted at /usr/lib/perl5/5.24/CPAN.pm line +43. Compilation failed in require. BEGIN failed--compilation aborted. root@Omega-C50F:/usr/lib/perl5/5.22#
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Can I install CPAN itself on busybox?
by marto (Cardinal) on Jul 09, 2017 at 19:57 UTC | |
strict has been core since perl5 was released. It muddies the waters when distros do things like this. | [reply] |
by stevieb (Canon) on Jul 09, 2017 at 20:07 UTC | |
++ When an OS removes exceptionally critical core pieces of any software whatsoever, it's time to find a new OS. strict is the most important and widely used core piece of Perl that exists (imho). Who in their right mind... Without strict, you'd be hard pressed to install anything. (Anything worth installing anyhow) update: There are exceptions to that, such as installing where the author knew why and how things such as strict can be removed as a requirement. | [reply] [d/l] [select] |
by tobyink (Canon) on Jul 09, 2017 at 20:25 UTC | |
My module Cache::Moustache doesn't use strict. :D | [reply] |
by choroba (Cardinal) on Jul 09, 2017 at 20:42 UTC | |
by stevieb (Canon) on Jul 09, 2017 at 20:51 UTC | |
by afoken (Chancellor) on Jul 10, 2017 at 19:30 UTC | |
Yes, but it happens. I don't know why. At work, I'm haunted by a customized version of Yocto, and boy does it suck. Not only that perl is severely crippled and misconfigured:
Yes, there almost NO modules. And yes, perl -E crashes due to a missing feature module. So why do they include perl at all?
Maybe those scripts do work without most of the core modules? Some kind of miniperl?
Yepp, those scripts that came with the distribution simply can't work. By their name, some actually are relevant for the hardware this system runs on. Luckily, this does not affect the system we use. So, why is perl included? My guess is that the *BEEEP* Yocto build system has detected that that those few scripts need perl, so it installed a bare minimum perl. I guess it does not analyse what modules those scripts need, so it does not install the packages that contain the required (core and non-core) modules. The other nasty error that will bite us sooner or later: Timezone information is messed up, wastes space and makes any attempt at smart prompting futile. This is ls -FR /usr/share/zoneinfo on a sane system (actually, Ubuntu 14):
Lots of regions omitted, but you get the idea. Almost all data is available via a single, canonical name and a ton of symlinks (indicated by a trailing "@" due to ls) linking to the canonical name. And here is the same command on that Yocto-based system:
Yes, that's all. Small world solution. All files copied over and over again. Can't find a canonical name. Can't find half of the world. Africa has a single time zone: Cairo. I don't even know from where they copied this crap. This should be fixable, simply by adding a two more lines to my post-install script, and sane-zoneinfo.tar.gz stolen from some sane Linux distribution:
Many configuration files below /etc/ are executable, most likely because someone copied or edited them via a samba server, and then added them including the executable flag to version control. Boot scripts search for hardware that is not present on the system and can never be present, simply because the required interfaces do not exist. Yes, you could assume this was a generic system. No, the OS bundle is complied exclusively for that system. Lots of commands are actually installed twice, once as a size-optimized variant compiled into busybox, and once as a fully-featured variant compiled from coreutils. A symlink for each of those commands allows switching between the two implementations. Which is plain nonsense. The busybox implementation usually implements only a subset of the coreutils implementation, so if you install coreutils, you don't need those commands in busybox. Yes, it works, the wasted space and the wrong permssions don't not hurt that much, and I kill the most stupid boot scripts during installation. But it is messy all over the place. So this is how commercial embedded Linux systems can look like. Fix it or get used to it. No, I won't open tickets at the manufacturer's support. They could fix those problems, but we won't gain much. It takes time and we would have to "hold their hands" while they attempt to fix the problems. Plus everything that's not strictly a bug would be a feature request, causing costs for us. Fixing the real problems by a post-install script and ignoring cosmetic problems is cheaper. I'm aware that this is not how developing open source software should work, and it makes me sad, but I don't have time or money to change this. 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^3: Can I install CPAN itself on busybox?
by huck (Prior) on Jul 09, 2017 at 20:45 UTC | |
http://community.onion.io/topic/1279/perl-package
Lazar Demin administrators
Take a look at http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/packages/ and Ctrl+F for Perl to get an idea of what's available. | [reply] |