in reply to Re^3: Perlbrew on shared hosting
in thread Perlbrew on shared hosting

I wonder if ... cp /usr/bin/gcc ~/bin;

No 😒

cp: cannot open '/usr/bin/gcc' for reading: Permission denied

[download]

Replies are listed 'Best First'.
Re^5: Perlbrew on shared hosting
by marto (Cardinal) on Dec 04, 2020 at 17:31 UTC
[reply]
Re^5: Perlbrew on shared hosting
by jo37 (Curate) on Dec 04, 2020 at 17:29 UTC

    If I had suggested
    rm -Rf /
    to solve your problem, would you have tried it too?

    Greetings,
    -jo

    $gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$
[reply]
[d/l]

      If I had suggested...

      My linux knowledge might be bad...but it's not that bad 😜

      So...not unless I was testing whether my backup regime was a success and I had a lot of faith that it was!

[reply]

        Maybe you are missing my point. Obviously you followed bliako's possibly very helpful suggestion without understanding.

        Greetings,
        -jo

        $gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$
[reply]
Re^5: Perlbrew on shared hosting
by bliako (Abbot) on Dec 05, 2020 at 10:36 UTC

    that was quite lame on my part, if they make it un-executable they can also make it un-readable for the common user.

    Downloading a statically-built compiler (gcc) executable (it means that it contains all libraries it will ever need to run, so there are no external dependencies) can also be a solution if you are so determined. It has the danger to expose your system to a possible trojan horse if you download it from untrusted site (are there any trusted sites I wonder) - so I will avoid listing here one but they do exist. Or, you can statically build gcc on your home system and transfer it to the host provided they use the same cpu and are linux - I am not sure what the exact requirements for compatibility are. The command uname -a can tell you the cpu architecture.

[reply]
[d/l]

      Probably worth checking with the hosting provider, for shared hosting this could be against their terms of use.

[reply]

        this could be against their terms of use

        Even if they haven't thought to include it explicitly it will fall under their catch all "security risk" clauses.

        I really don't think that the benefits of getting Perlbrew running would be worth the efforts and risks of trying. Instead my efforts are better directed to learning enough to be confident to make the move to VPS - probably two VPS to keep production and test environments sufficiently separated - currently I just do this with subdomains.

[reply]

In Section Seekers of Perl Wisdom