sbin | Secure paste bin application | SSH Utils library

Currently (2022-02-05), CRAN builds R binaries for Apple silicon using Apple clang (from Command Line Tools for Xcode 12.4) and an experimental build of gfortran.

If you obtain R from CRAN (i.e., here), then you need to replicate CRAN's compiler setup on your system before building R packages that contain C/C++/Fortran code from their sources (and before using Rcpp, etc.). This requirement ensures that your package builds are compatible with R itself.

A further complication is the fact that Apple clang doesn't support OpenMP, so you need to do even more work to compile programs that make use of multithreading. You could circumvent the issue by building R itself and all R packages from sources with LLVM clang, which does support OpenMP, but this approach is onerous and "for experts only". There is another approach that has been tested by a few people, including Simon Urbanek, the maintainer of R for macOS. It is experimental and also "for experts only", but seems to work on my machine and is simpler than trying to build R yourself.

Warning: These instructions come with no warranty and could break at any time. They assume some level of familiarity with C/C++/Fortran program compilation, Makefile syntax, and Unix shells. As usual, sudo at your own risk.

I will try to address compilers and OpenMP support at the same time. I am going to assume that you are starting from nothing. Feel free to skip steps you've already taken, though you might find a fresh start helpful.

I've tested these instructions on a machine running Big Sur, and at least one person has tested them on a machine running Monterey. I would be glad to hear from others.

1. Download an R binary from CRAN here and install. Be sure to select the binary built for Apple silicon.

2. Run

The error says that either you haven't got Django installed or didn't activate the virtual environment in which the Django was installed. Make sure that you check the list of installed packages and find Django in there, via:

You have to update tools for AVD in the IDE. Android Emulator is 31.2.6

Have you tried editing your web server service file, nginx.service or apache2.service? I had this problem and solved it by removing the line:

Once you can copy io.delta:delta-core_2.12:1.0.0 JAR file to $SPARK_HOME/lib and restart, this error goes away.

I worked it out; the issue was that I didn't realise that when you install Passenger as a dynamic module, you still need to do the same config as with a regular install. In particular, in your nginx.conf, you need to add this to the http block:

Based on the various comments ...

1. You have Java 17 installed ... manually ... in /opt/jdk17
2. You have JAVA_HOME pointing on the base of the Java 17 installation. I assume that there is (for example) a /opt/jdk17/bin/java executable.
3. The Java 17 installation directory is NOT on the command search path (PATH).
4. The search path is finding /usr/bin/java ... which (in your case) says Java 16 when you run java -version.
5. Your system has the "/etc/alternatives" system installed, but sudo update-alternatives --config java says that only Java 16 is available.

So ...

The "alternatives" mechanism creates and maintains symlinks to various switchable commands. If you run ls -l /usr/bin/java for example, I expect that you will see that it is a symlink. When you run update-alternatives, it will attempt to update the symlinks. But it can only do this for commands and command versions that it knows about.

Right now ... update-alternatives does not know about Java 17. It doesn't know it is installed, or where it is installed.

If you had installed Java 17 from the package manager, then the config files that tell update-alternatives about Java 17 would have been added too.

Solutions, ordered from "best" (1) to "worst".

1. Remove your manual install of Java 17 and install it from the package manager. You might need to find / add an "experimental" Debian package repo to do this. (I get the impression that the official Debian repo managers tend to be rather slow in picking up new stuff.)

2. Carefully read the documentation in man 1 update-alternatives and update-alternatives --help and then use the --install and --slave commands to tell it about Java 17.

3. Find the Java symlinks and manually replace them with symlinks to the Java 17 versions of the executables. (Be careful ...)

4. Add /opt/jdk17/bin to the start of your PATH. (Be careful ...)

5. Just use the full pathnames; e.g. /opt/jdk17/bin/java rather than java.

I also came across this:

• Java 17 on the Raspberry Pi which includes (among other things) example commands for adding Java 17 to the alternatives system. It also mentions using sdkman.

• How to Install Java 17 (JDK 17) on Debian 11. There is a comment that says:

  "Awesome! Thanks. This Debian package works on Raspberry Pi's Raspian 64-bit Bullseye as of posting. Only method that works without manually downloading packages and attempting to install. :)".

  But I see that you have a 32-bit Raspberry Pi ...

As you can see in strace, the execve command executes as: execve("/bin//nc", ["/bin//nc", "/bin//nc-e //bin/bash -nvlp 4455"], NULL) = 0 It seems to be taking the whole /bin//nc-e //bin/bash -nvlp 4455 as a single argument and thus thinks it's a hostname. In order to get around that, the three argv[] needed for execve() is pushed seperately. argv[]=["/bin/nc", "-e/bin/bash", "-nvlp4455"] These arguments are each pushed into edx, ecx, and ebx. since ebx needs to be /bin/nc, which was already done in the original code. we just needed to push 2nd and 3rd argv[] into ecx and edx and push it into stack. After that we just copy the whole stack into ecx, and then xor edx,edx to set edx as NULL.

Here is the correct solution:

The problem here seems to be Python 3.10.1!

I used anaconda to create a new virtual environment with Python 3.8.12, installed brownie using pipx install --python python3.8 eth-brownie and it worked!

The trick here was, to also tell pipx to use another python version, otherwise it would create a dependency to the global python version, which is python 3.10 in my case.