in reply to Re: Using STDIN after exec() with ActiveState Perl
in thread Using STDIN after exec() with ActiveState Perl

I need the exec because I have to adjust the environment variables seen by perl at launch time (see programatically setting the LD_LIBRARY_PATH for the exact reason).
  • Comment on Re^2: Using STDIN after exec() with ActiveState Perl

Replies are listed 'Best First'.
Re^3: Using STDIN after exec() with ActiveState Perl
by LanX (Saint) on Jun 21, 2015 at 19:52 UTC
    Ehm... What's wrong with setting $ENV{PATH} in a BEGIN block?

    update

    Providing you are not allowed to set the correct environment in the registry.

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

      The DLL to load is not known at script start.
        You are getting sarcastic answers because you are asking the wrong questions without providing enough informations even after multiple attempts.

        Please state your use case clearly, such that we can help you.

        See also How do I post a question effectively?

        PS: welcome in the.monastery! =)

        Cheers Rolf
        (addicted to the Perl Programming Language and ☆☆☆☆ :)
        Je suis Charlie!

        Great, then you don't need a begin block :)
Re^3: Using STDIN after exec() with ActiveState Perl
by Anonymous Monk on Jun 21, 2015 at 19:39 UTC
    windows doesn't have LD_LIBRARY_PATH
      I know. I use PATH instead on Windows and it works. The only problem is this STDIN being multiplexed.

      edit: actually it's not even for the PATH environment variable that I need the exec, it's for setting an environment variable that can be seen by a dynamic library called by my script.

        I know. I use PATH instead on Windows and it works. The only problem is this STDIN being multiplexed.

        Windows isn't linux, PATH is not LD_LIBRARY_PATH , you don't need exec on windows