Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re^8: Installing (lotsa) modules

by marto (Cardinal)
on Jan 25, 2021 at 11:36 UTC ( #11127436=note: print w/replies, xml ) Need Help??


in reply to Re^7: Installing (lotsa) modules
in thread Installing (lotsa) modules

You can't compile XS code on Windows and move it to Linux. As mentioned previously, run a VM locally the same OS and architecture as your target, that way you can compile in a fairly straight forward manner, and transfer to your host.

Replies are listed 'Best First'.
Re^9: Installing (lotsa) modules
by jszinger (Scribe) on Jan 26, 2021 at 17:33 UTC
    This is why package management systems such as deb, RPM, ports, and so on were invented. The software could be built once and installed many times. There was even one available for Solaris!. For example, both Fedora and Ubuntu have over 3000 perl modules waiting to be installed.

      Not from Windows to *NIX, you can't just copy binary stuff built on one and expect it to work on the other. Reading OPs post history will reveal current hosting limitations.

      If I'm not mistaken, these build systems rely on the system perl. I never, ever allow anything to come remotely close to my system perl (or python etc).

        I never, ever allow anything to come remotely close to my system perl (or python etc).

        Why? If the vendors repo for the system perl has modules, those were compiled and tested with the system perl and just work, just like they would with any custom perl installed with e.g. perlbrew.

        For years I have just used the system perl and the system build system to compile and install modules (as *.deb, *.rpm, you name it) not present in the vendor's repo, with no adverse effect to the system perl or the system itself.

        The system perl often comes along with patches (Debian for instance has a long patchlist) which are probably optimizing perl for the system at hand. If I were to compile the same perl version with the systems compiler, its libraries and those patches, it would be no different from the system perl.

        And there is always local::lib.

        perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
Re^9: Installing (lotsa) modules
by Bod (Deacon) on Jan 25, 2021 at 12:39 UTC
    run a VM locally the same OS and architecture as your target

    Therein lies the difficulty...I have no idea of either the OS (other than Linux) or architecture of the target virtual machine.

    It is not something I am going to spend much time on.
    When it becomes mission critical, and when my Linux confidence improves, I will upgrade to VPS or dedicated server which will make the issue obsolete.

      "have no idea of either the OS (other than Linux) or architecture of the target virtual machine."

      If only we as a species had one (or more) ways to search for answers to such things :P

        As you yourself said marto in Re^10: Perlbrew on shared hosting
        As your skills develop no doubt you'll consider alternatives

        As yet, those skills haven't developed sufficiently. Instead I've been implementing templating and replacing require *.pl; with modules.

        Probably more useful skills to me than learning to identify the architecture of a virtual machine that will be replaced before very long with one of known architecture and over which I have more control.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11127436]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (2)
As of 2021-09-19 17:02 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?