Continuing without passenger_native_support.so

[Leo baltus]

Hi,

Running passenger-4.0.40 compiled using ruby-1.9.3 in its PATH

it seems that when an app is running with:

<VirtualHost ...
PassengerRuby /path/to/bin/ruby
</VirtualHost>

where /path/to/bin/ruby is a wrapper setting env-vars and calling ruby-2.1

I see:
App 1385 stderr:  --> Skipping compiling of passenger_native_support.so
App 1385 stderr:  --> Downloading precompiled passenger_native_support.so for the current Ruby interpreter...
App 1385 stderr:      (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable)

It seems to matter with what ruby passenger is built. Im I right?

If passenger supports multiple rubys, should it be built with all ruby's I would like to use?

meanwhile passenger continues:
App 1385 stderr:  --> Continuing without passenger_native_support.so.

How bad is that?

[Hongli Lai]

On Fri, May 16, 2014 at 4:22 PM, Leo baltus <leo.b...@omroep.nl> wrote:
> Hi,
>
> Running passenger-4.0.40 compiled using ruby-1.9.3 in its PATH
>
> it seems that when an app is running with:
>
> <VirtualHost ...
> PassengerRuby /path/to/bin/ruby
> </VirtualHost>
>
> where /path/to/bin/ruby is a wrapper setting env-vars and calling ruby-2.1
>
> I see:
> App 1385 stderr: --> Skipping compiling of passenger_native_support.so
> App 1385 stderr: --> Downloading precompiled passenger_native_support.so
> for the current Ruby interpreter...
> App 1385 stderr: (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to
> disable)
>
> It seems to matter with what ruby passenger is built. Im I right?

No, Passenger doesn't care. It only cares which Ruby you instructed it
to run your app with. Passenger automatically tries to build a
native_support.so for every Ruby interpreter it hasn't encountered
yet.

> meanwhile passenger continues:
> App 1385 stderr: --> Continuing without passenger_native_support.so.
>
> How bad is that?

Not bad. Very very small impact. You can ignore this and everything
will still work fine.

--
Phusion | Web Application deployment, scaling, and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Leo baltus]

Op vrijdag 16 mei 2014 17:11:48 UTC+2 schreef Hongli Lai:

On Fri, May 16, 2014 at 4:22 PM, Leo baltus <leo.b...@omroep.nl> wrote:
> Hi,
>
> Running passenger-4.0.40 compiled using ruby-1.9.3 in its PATH
>
> it seems that when an app is running with:
>
> <VirtualHost ...
> PassengerRuby /path/to/bin/ruby
> </VirtualHost>
>
> where /path/to/bin/ruby is a wrapper setting env-vars and calling ruby-2.1
>
> I see:
> App 1385 stderr:  --> Skipping compiling of passenger_native_support.so
> App 1385 stderr:  --> Downloading precompiled passenger_native_support.so
> for the current Ruby interpreter...
> App 1385 stderr:      (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to
> disable)
>
> It seems to matter with what ruby passenger is built. Im I right?

No, Passenger doesn't care. It only cares which Ruby you instructed it
to run your app with. Passenger automatically tries to build a
native_support.so for every Ruby interpreter it hasn't encountered
yet.

I would like it to not even try that, however setting 
export PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0
does not seem to silence passenger. Am I misunderstanding something?

> meanwhile passenger continues:
> App 1385 stderr:  --> Continuing without passenger_native_support.so.
>
> How bad is that?

Not bad. Very very small impact. You can ignore this and everything
will still work fine.

it''s not easily ignored because it makes e great fuss, trying to download and compile ... :)

Seriously, if it doesn't make that much difference why even bother in the first place? 

[Hongli Lai]

On Mon, May 19, 2014 at 4:26 PM, Leo baltus <leo.b...@omroep.nl> wrote:
> I would like it to not even try that, however setting
> export PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0
> does not seem to silence passenger. Am I misunderstanding something?

You can have passenger_native_support.so precompiled by running
'passenger-config build-native-support' using that particular Ruby
interpreter.

> Seriously, if it doesn't make that much difference why even bother in the
> first place?

Looks better in benchmarks, which certain people care about.