Does libboost-python have a multiarch support for armhf? (DEBIAN) - compilation

Short
Does libboost-python have a multiarch support for armhf?
Elaborate
I want to install libboost-python on a amd64 bit machine, for armhf cross compilation purposes. Thus it should be armhf. However, in the dependency chain libboost-python will try to install python, and since the first package is :armhf, python also should be armhf. Which cases a failure, because one of the post scripts runs the python interpreter, and it cannot be run since the interpreter is armhf while the machine is amd64.

As far as I've investigated, libboost-python Debian package does not support multiarch. A possible soultion for the problem in the post is using qemu in order to emulate a "native" environment for building packages.

Related

IRAF for Mac m1

Hi I'm trying to install IRAF with anaconda I follow these steps, but when I run iras, and I want to make something, this program doesn't recognize the commands of IRAF
i follow this tutorial: https://astroconda.readthedocs.io/en/latest/installation.html
I don't know how to fix it.
The Astroconda IRAF is a 32-bit version and does not work on M1 Macs, since they are not able to run 32-bit code.
To install IRAF for an M1 Mac, you should compile it manually, as described in https://iraf-community.github.io/install. This installs the latest 64-bit IRAF version. PyRAF (for Python 3) can then simply installed with pip3, see https://iraf-community.github.io/pyraf.html.
However, it is not recommended to start with IRAF unless there is a real need for it. IRAF is old software with an uncertain future and no institutional support. The Astropy Python package and its ecosystem provide good alternatives for many tasks of IRAF. https://astropy.org

Installing OpenAL (or a similar package) on W7

I want to install OpenAL Haskell bindings for Windows. When I try cabal install alut I get:
Resolving dependencies...
Configuring OpenAL-1.4.0.2...
cabal: The package has a './configure' script. This requires a Unix
compatibility toolchain such as MinGW+MSYS or Cygwin.
Installing MSYS or Cygwin is absolutely not an option. runghc setup configure on the source yields the same thing. This leads me to the following:
How can I install OpenAL with just an installation of the Haskell Platform? I know mingw comes with the Haskell Platform on Windows. Can I use just that to execute this script?
Is there a package that can play audio that installs with cabal on Windows 7 AND Unix based systems?
The source contains hundreds of directives designed for the configure script, which doesn't work on Windows. Is there a version of the source which is platform specific, ie, the script has already been run in a windows environment?
Edit: Context for the problem:
I have a Haskell program, which among other things, plays sound. It is going to be used for demonstration/interactive presentation to students. The computers in the lab run Windows 7. They have the Haskell Platform installed, but not MSYS or Cygwin. I have about 45 minutes to complete this, which doesn't leave time for the installation of needlessly complex and essentially pointless software. If I could get Windows-compatible source code, I could just distribute it with the program I wrote. All the packages I need besides this one will cabal install just fine; this is also a good introduction to package management.
Edit2: cabal install fails with Cygwin installed, as does runghc setup configure

Installing gcc 4.8 on Debian

I want to start playing around with some of the newer C++11 features and it appears that the best support for this is with gcc 4.8, and Squeeze ships with 4.4.5.
However, I don't want to cause any "damage" to my current setup. What's the best way to get both versions of gcc running side-by-side? I'm concerned mostly at the large number of dependencies and that taking them all in to my current system may render it unstable.
Has anyone managed to do this, and what are the steps involved?
Failing that, I'll probably just create a VM and run an "unstable" Debian under that but it's a less-than-ideal solution.
If you install GCC from source just make sure you don't install it to /usr and it won't mess anything up. If you install it as your own user, not root, then there is zero chance of messing up the system.
See http://gcc.gnu.org/wiki/InstallingGCC for the almost-idiot-proof minimal configuration.
I have various versions built as my user and installed in ~/gcc/4.X for various X.
The only thing to be aware of using that set up is that the shared libraries for the new version aren't in the dynamic linker's default search path, so you need to use LD_LIBRARY_PATH or some other solution to ensure executables find the libs from 4.8, see the libstdc++ FAQ and the page it links to in the manual
I use a wrapper script call g++11 which simply calls the new version of GCC with -std=gnu++11 and passes a flag to the linker telling it to set the path to the 4.8 libs in the executable:
$HOME/gcc/4.8/bin/g++ -Wl,-rpath,$HOME/gcc/4.8/lib64 -std=gnu++11 -Wall -Wextra -g "$#"
I had the same problem, and didn't want to fully upgrade to testing.
Jessie (testing) now contains g++-4.8 which is compliant with C++11.
I used apt-pinning in the following way:
A source to jessie was added to /etc/apt/sources.list:
deb http://ftp.uk.debian.org/debian/ jessie main non-free contrib
/etc/apt/preferences was edited as such:
Package: *
Pin: release n=wheezy
Pin-Priority: 900
Package: gcc*
Pin: release n=jessie
Pin-Priority: 910
Then,
$ sudo aptitude update
$ sudo aptitude install gcc/jessie
At which point I selected the second presented option to resolve dependencies fully.
Debian has the package under the name gcc-4.8 (or for the c++ compiler, g++-4.8). Installing those packages will not mess up your OS, as long as you do not rename it to g++. The package is listed as experimental though.
Information on the package is here.
Update: g++-4.8 is now in testing, but an updated package is in unstable
Quick ones:
Just upgrade to testing, it is rock-solid and offers you several concurrent gcc versions. Similar for Ubuntu, on 12.10 I have gcc/g++ 4.4, 4.5, 4.6 and 4.7 in parallel.
Try the Debian backports archive, it may have a port of gcc 4.8.
Use virtualization: I prefer libvirt / kvm which is incredibly lightweight on Linux as it is kernel based. My amd64 server has two other 32 bit installations for that very reason.
Not really a SO question...
Have you tried chroot to install a newer Debian flavor?
you can play around without fear to break you working system.
install a Debian flavor that support you gcc version desired.
install a gcc version manually without affecting you working system.
http://wiki.blender.org/index.php/Dev:Doc/Building_Blender/Linux/Chroot

z3 install in Redhat platform

Can the latest z3 be installed in the Redhat linux platform? There is no mention to this platform in the https://github.com/Z3Prover/z3
As you pointed out, we currently do not provide pre-compiled binaries for RedHat Linux. We currently only provide pre-compiled binaries for: Ubuntu and Debian. We also regularly compile Z3 on Fedora.
That being said, you should be able to compile Z3 on RedHat Linux without problems. In particular, we have managed to compile the unstable (work-in-progress) branch in many different platforms.
See this related question:
Installation of Z3 on a posix system without python?
This link has instructions on how to compile Z3 on Linux.

How to build GCC 4.7 on Windows?

How to build GCC 4.7 on Windows?
You are not finding instructions on how to do this because you cannot natively use gcc in Windows. Your options are either to use gcc through Cygwin [installation instructions] or install the MinGW port [installation instructions].
You can also find links to these projects on the Installing GCC: Binaries page.
Well, gcc 4.7 has not yet been released (it will be released in a few months, i.e. spring 2012).
If your system is Windows then I am sorry for you, Linux is so much better :-) More seriously, you should search for cygwin gcc. I cannot help you in that case.
What did you try? Building GCC (even on Linux) is not an easy task. Some hints (which I guess are also relevant to cygwin & windows).
Always configure and build the compiler in a build tree outside of the source tree. (this is a common mistake).
take care of the many dependencies (and their versions), like the Parma Polyhedra Library, Cloog, etc ...
some features of GCC are not available on Windows. In particular plugins.
I would suppose that installing the binary of an older variant of cygwin gcc (and all the related packages) will help.
But really, I know nothing about Windows. And if you really want a very recent GCC and you cannot install Linux (or build GCC cygwin), you might perhaps consider running Linux in an emulator or virtual machine.

Resources