search for: shebangs

On FreeBSD we cannot go through the shell script (./nbdkit). Instead replace the path with a direct link to both the nbdkit binary and locally compiled plugin. Note this does not go through valgrinding when you run ‘make check-valgrind’ so that needs to be fixed at some point in the future. Thanks: François Revol and Eric Blake. See also:

On 11/13/18 7:40 AM, Richard W.M. Jones wrote: >> (I think the error message is "incorrect ELF header") could be >> something to do with the way we use shebangs (#!). IIRC this also >> fails on FreeBSD so probably nbdkit is doing something which is not >> correct POSIX. > POSIX says that #! shebangs are undefined behavior. You're at the mercy of each operating system, because there is no portable solution across all systems. > I...

On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: > if you leave it out the script will run in whatever environment it > currently is in. I'm reasonably certain that a script with no shebang will run with /bin/sh. I interpret your statement to mean that if a user is using ksh and enters the path to such a script, it would also run in ksh. That would only be true if you

...ion was added 4 years ago :-/ so it could be time to upgrade. This error: ./test-shebang-perl.sh: PID file was not created rect ELF header FAIL test-shebang-perl.sh (exit status: 1) (I think the error message is "incorrect ELF header") could be something to do with the way we use shebangs (#!). IIRC this also fails on FreeBSD so probably nbdkit is doing something which is not correct POSIX. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs f...

...now be at least compatible with both python2 (py2) and python3 (py3), some of them already are already py3 only. The build system still depends on Python in a few place, but it explicitly mentions Python3_EXECUTABLE, and the main dependency (llvm-build) is currently being removed in D89142. The shebangs have already been harmonized in D83857: some mention /usr/bin/env python, some mention /usr/bin/env python3, and none mention python2 anymore. It would be great to have all script use the same shebang, PEP394 [1] makes it (relatively) clear that in our case, explicitly requiring python3 is the way...

On Fri, Nov 22, 2019 at 02:55:31PM -0600, Eric Blake wrote: > Unrelated side topic: in your recent addition of eval.sh, you > wondered if we should promote it to a full-blown plugin rather than > just an example script. But reading 'man nbdkit-sh-plugin', there > is no mention of turning an executable script into a full-blown > plugin via a shebang, the way that python

All, I have a script that runs script/runner via the shebang mechanism at the top o the file, like so: #!/usr/bin/env ./script/runner This works fine in development, how would I get it to run in non-development environments? Thanks, Wes -- Posted via http://www.ruby-forum.com/.

On Sat, Nov 23, 2019 at 01:58:02AM +0200, Nir Soffer wrote: > On Fri, Nov 22, 2019 at 11:07 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > On Fri, Nov 22, 2019 at 02:55:31PM -0600, Eric Blake wrote: > > > Unrelated side topic: in your recent addition of eval.sh, you > > > wondered if we should promote it to a full-blown plugin rather than > >

On Fri, Nov 22, 2019 at 11:07 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Nov 22, 2019 at 02:55:31PM -0600, Eric Blake wrote: > > Unrelated side topic: in your recent addition of eval.sh, you > > wondered if we should promote it to a full-blown plugin rather than > > just an example script. But reading 'man nbdkit-sh-plugin', there > >

The path to bash on FreeBSD is /usr/local/bin/bash. --- docs/make-links.sh | 2 +- nbdkit.in | 2 +- tests/make-pki.sh | 2 +- tests/make-psk.sh | 2 +- tests/test-blocksize.sh | 2 +- tests/test-cache.sh | 2 +- tests/test-captive.sh | 2 +- tests/test-cow.sh | 2 +-

On 04/24/2015 09:59 AM, Steve Lindemann wrote: > > A script with no shebang will run in the environment of the account > running the script. Bad test on my part, apparently. $ python >>> import os >>> os.execv('/home/gmessmer/test', ('test',)) Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError:

Hi, I''m new at rails and am in the midst of deploying my first app to a test server. The app was developed on windows. I used Capistrano to deploy, and found a few issues: 1) I must chmod 755 dispatch.cgi each time I deploy 2) script/parse/reaper also doesn''t have the executable attributes so the deployment fails. 3) database.yml as checked out from svn isn''t

On Sat, Nov 23, 2019 at 5:46 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Sat, Nov 23, 2019 at 01:58:02AM +0200, Nir Soffer wrote: > > On Fri, Nov 22, 2019 at 11:07 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > > > On Fri, Nov 22, 2019 at 02:55:31PM -0600, Eric Blake wrote: > > > > Unrelated side topic: in your recent

Dear R-devel, Recently I ran into trouble installing two separate packages, nloptr and ncdf4, both due to the same issue: they have scripts that have the shebang `#! /bin/sh', but have bashisms in them, i.e. non-POSIX-compliant bash scripts. I use dash [1] as my shell environment, since it's about 4x as fast as bash. It looks like it's recently also become the default shell for

On Fri, April 24, 2015 12:04 pm, John R Pierce wrote: > On 4/24/2015 9:47 AM, Gordon Messmer wrote: >> On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: >>> if you leave it out the script will run in whatever environment it >>> currently is in. >> >> I'm reasonably certain that a script with no shebang will run with >> /bin/sh. I interpret your

On 24 February 2016 at 19:49, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Great! I'll circle around to this at some point. Despite the "obvious" > nature of it I still am wary of underestimating the cruftiness of the > buildbots, so I'll probably do it some time at night when the bots are > mostly green so that I can easily see if any bots

I just setup switchtower and I am very happy with it. Just one thing is giving me some headache: My development machine is windows and my deployment host is Unix. Each time I deploy I need to make dispatch.fcgi executable. I wrote my own task for that. But does there exist any smarter way to get this automated ? I think Subversion offers some possiblity to declare a file as executable, but no idea

On 11/22/19 1:53 PM, Richard W.M. Jones wrote: > To avoid breaking existing plugins, Python plugins wishing to use > version 2 of the API must opt in by declaring: > > def api_version(): > return 2 > > (Plugins which do not do this are assumed to want API version 1). Could we also permit the python code to declare a global variable instead of a function? But a

What do you think about adding a shebang line to the samples so they can be launched on linux/mac like you can on windows? Roy

Please forgive my ignorance but I need a explanation of how to accomplish the following since I cannot figure it out from the documents. I have a Ruby script with a shebang line that looks like this: #!/usr/bin/env ruby On one particular host I have two Ruby interpreters installed; one the CentOS base version 1.8.6 in /usr/bin/ruby the other version 1.8.7 in /usr/local/bin/ruby. In my shell