How do you find out which version of typescript/tsc you run under Ubuntu? There's no manual or --version switch for tsc.
Since I use Ubuntu 12.04, I installed an older version of node without my knowing, which in turn installed an older version of typescript. Appareantly, the old tsc command does not have the --version switch, but the new one has.
In any version of TypeScript if you type in tsc without any arguments it shows you its version in the help message.
Related
I want to install clang-3.4 , opt-3.4 and llc-3.4 on my ubuntu 16.04.
I want specific version 3.4 only.
opt-3.4: It is LLVM optimizer.
llc-3.4: It is LLVM static compiler.
Running the installation command gives me error:
$ sudo apt-get install clang-3.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package clang-3.4 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
clang-5.0:i386 clang-3.9:i386 clang-3.8:i386 clang:i386 clang-5.0 clang-3.9 clang-3.8 clang clang-4.0:i386 clang-4.0 clang-3.7:i386
clang-3.6:i386 clang-3.5:i386 clang-3.7 clang-3.6 clang-3.5
E: Package 'clang-3.4' has no installation candidate
How can I install the 3.4 version of packages?
EDIT:
Answers on how to port the project to a recent version of clang is also welcome.
I am running MacOS Mojave Version 10.14.1. I am attempting to install the avr embedded development environment.
The command 'brew tap osx-cross/avr' works correctly however when the command 'brew install avr-libc' is used the following error is produced error
This produces a problem as files in c cannot be compiled due to avr-gcc being unavailable.
Any help and advice would be appreciated.
as #nos said, you need to run brew install avr-gcc.
More info here: https://github.com/osx-cross/homebrew-avr#installing-homebrew-avr-formulae
This worked for me: brew tap osx-cross/avr && brew install avr-gcc
Needed to expand brew's options of available software, as well as reference the updated avr-gcc instead of avr-libc.
I'd like to install the FLEXPART program on my kubuntu 14.04 x64 LTS machine, they require the installation of the grib-api and jasper library first as mentionned in the website (http://flexpart.eu/wiki/FpInstall).
the issue is that i can't achieve correct installation of these two packages and therefore the proper install of FLEXPART. could someone give me the right way to install these two libraries in order to make the model run?
there is a precompiled package of FLEXPART 9.02 for ubuntu distribution
http://packages.ubuntu.com/trusty/utils/flexpart
I've compiled a C program under Ubuntu 12.04, built a Debian package out of it, and want to install it on a server running Debian Lenny.
Last time I did that (about two months ago) it worked: I could install the package and run the binary. But now I get the following error message:
(binary's name): /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by (binary's name))
Other than upgrading my machine to Ubuntu 12.4, the only significant change we've brought to the code is a call to strdup(), for which I had to enable the _POSIX_C_SOURCE=200809L feature test macro.
Upgrading the server to the latest Debian version is not my preferred option as it is not under my direct control.
How do I fix this problem?
I think the critical bit of info here is 'upgrading my machine'. So when this worked before, you were building and packaging on something earlier than 12.04? If so, then the issue is that 12.04 now ships with a newer version of libc (apparently 2.14), and your binary now records a dependency on that version of libc. When you try to run on Lenny, which likely uses an older version of libc, the linker detects that the Lenny version does not support the 2.14 API, and fails.
I think the best way forward is probably to do your development and testing on 12.04, and then when you want to create packages for a specific Debian release, use pbuilder or similar to create debs. This will ensure that the libraries used for the packaging build match the target platform.
I just got Macports installed on my mac, of which os version is Snow Leopard (10.6). I used Macports to install several packages through 'sudo port install' command, and all these packages are reported active after the installation. I just wonder that whether these packages are really working? For example, macports tells me that 'gcc44 #4.4.2_0 (active)', however in python it says '[GCC 4.0.1 (Apple Inc. build 5493)] on darwin'.
So I just want to know that if there is some problem with my method of installing or my macports needs some configuration after installation?
Any help is appreciated! I am really new in Mac OS.
I believe Python is declaring the version of gcc used to build it which should be the gcc installed on your Mac i.e. the version that came with the Mac OS Development tools. This should be located in /usr/bin/gcc.
You should find the gcc version matches when you execute
/usr/bin/gcc -v
I do not think anything is wrong with your setup or configuration. It just shows Python was compiled using the gcc provided by Apple
Macports installs software not to conflict with the versions provided by Apple. If they replaced the C compiler and libraries, really bad things might happen when Apple provided operating system updates.
gcc is the command for Apple's version of gcc, at /usr/bin and version 4.0.1 for Leopard.
gcc-mp-4.4 is the command for gcc version 4.4 as provided by MacPorts, located at /opt/local/bin.
Similarly there will be versions of python in /opt/local/bin.
Like houmam, I prefer to explicitly invoke versions by name. If you want to connect particular versions to python, I think that the MacPorts package python_select (this has now been replace by port select python) implements this by using symbolic links. I've never used it.
It probably is just that compiler that was picked by the build was that installed by XCode. You can try typing which gcc to see which one is in your path. The macports one would by default be in /opt/local somewhere.