Cannot install Anaconda on mac - linux

first, I tried command
./Miniconda3-latest-MacOSX-x86_64.sh
and it reports that
line 296:
/data/keeling/a/xinyix3/miniconda/pkgs/python-3.6.0-0/bin/python:
cannot execute binary file ERROR: cannot execute native osx-64 binary,
output from 'uname -a' is: Linux keeling.earth.illinois.edu
2.6.32-642.3.1.el6.x86_64 #1 SMP Tue Jul 12 11:25:51 CDT 2016 x86_64 x86_64 x86_64 GNU/Linux
I am really new to Linux. Is there any suggestions of failure of installation?

You seem to be running the wrong binary/script for Miniconda. Use the Miniconda3-latest-Linux-x86_64.sh script if you're on linux, not the OSX one.

Related

Runtime error "undefined symbol g_malloc0_n" - but only on old Debian5

We have a legacy Linux application, written in C, using GTK.
We compile it on Ubuntu14/32-bit, we can also launch it
In production, we run it on Debian10/32-bit
We have some very old hosts, which runs Debian 5. The old version of the application runs on Debian 5, but when we compile a new one, we got a runtime message:
.../bin/gui: symbol lookup error: .../lib/libmkt.so: undefined symbol: g_malloc0_n
It's strange, because nm finds it:
$ nm .../lib/libmkt.so | grep g_malloc
U g_malloc0
U g_malloc0_n
Also the application has a good reference entry to the library:
$ ldd .../bin/gui | grep libmkt
libmkt.so => .../lib/libmkt.so (0xb7257000)
This is happening only on the old machine with Debian 5:
$ uname -a
Linux kiosk 2.6.26-2-686 #1 SMP Mon Aug 30 07:01:57 UTC 2010 i686 GNU/Linux
On the new machine, with Debian 10, the application starts:
$ uname -a
Linux kiosk 4.19.0-17-686-pae #1 SMP Debian 4.19.194-1 (2021-06-10) i686 GNU/Linux
The developer machine with Ubuntu14, the application starts:
$ uname -a
Linux ubuntu-build-server 4.4.0-142-generic #168~14.04.1-Ubuntu SMP
Sat Jan 19 11:28:33 UTC 2019 i686 i686 i686 GNU/Linux
We start the application with LD_LIBRARY_PATH=.../lib .../bin/gui, we have a bunch of .so files in the .../lib directory, including the .../lib/libmkt.so, which indicates the error.
My hint is that the compiler uses some feature for libmkt.so, which the 2.6 kernel does not like, but I haven't found such issue on the internet.
UPDATE: .../lib/libmkt.so does not contain the missing g_malloc0_n symbol, but it refers to the GTK library, which does. What should I do in order to find such second-hop symbols?

pyAlsaaudio install on openSUSE

I'm trying to install pyAlsaaudio on my openSUSE distro
Output of uname -a: Linux linux-0cd5 4.12.14-lp150.12.48-default #1 SMP Tue Feb 12 14:01:48 UTC 2019 (268f014) x86_64 x86_64 x86_64 GNU/Linux
I downloaded the source from this link,
http://larsimmisch.github.io/pyalsaaudio/pyalsaaudio.html
which includes a py setup file.
Initially I didn't have the gcc compiler installed, so I just installed it.
Snipped output of gcc -v: gcc version 7.3.1 20180323 [gcc-7-branch revision 258812] (SUSE Linux)
The setup.py file is still giving me issues, I think because I am missing the alsa/asoundlib.h file, similar to this thread:
https://ubuntuforums.org/showthread.php?t=1586707
However, the solution there doesn't work for openSUSE, there isn't a libasound2-dev available for openSUSE.
Any ideas?
I just found an answer for this here:
https://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/069794.html
I used the following command:
sudo zypper install -C 'pkgconfig(alsa)'
which pointed me to a package I wasn't aware of - "alsa-devel". I wasn't able to find this package when I searched for things like "libasound"
Now I have the proper alsa/asoundlib.h file which is something that the creators of pyalsaaudio note could cause issues if it is absent.
setup.py compiles without issues now! Hope this helps someone else avoid losing 2 hours of googling!

IDA doesn't work inside screen

I am trying to run idal64 (IDA pro) inside a screen session, but I receive this error:
TVision error: Can not load libcurses.so
Without libcurses can work only with xterm/linux
Aborted (core dumped)
I installed 'libncurses5-dev', 'libncursesw5-dev', 'lib32ncurses5-dev' and 'libx32ncurses5-dev', but nothing changed.
This library seems to be correctly installed:
#find / -name libcurses.so
/usr/lib32/libcurses.so
/usr/lib/x86_64-linux-gnu/libcurses.so
/lib/libcurses.so
/lib64/libcurses.so
/lib32/libcurses.so
My machine info:
Linux 3.13.0-49-generic #83-Ubuntu SMP Fri Apr 10 20:11:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
The weird thing is that IDA correctly works outside screen.
Any idea?
I ran into the same issue running idal in tmux, and determined that
env TERM=xterm /path/to/idal
works around this issue for 32-bit idal. Haven't tried idal64 but I expect this will work for you as well.

Make kernel module for BeagleBoneBlack

I have a BBB with Linux pre-installed from the vendor. Here is output from uname -a:
Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux
I am trying to make a Kernel Module, for example HelloWorld.ko for it.
I cloned code from git://github.com/RobertCNelson/linux-dev.git and checkout origin/am33x-v3.8. After I built a module on it and tried to insmod it on my BBB, I got error message:
Error: could not insert module Hello.ko: Invalid module format,
I double checked version of the kernel, it is 3.8.13-bone53. Is this the root cause? Where can I get the "exactly" matched kernel source tree for it? There is no version named 3.8.13 in my cloned git commit tree.
Thanks for your help!

libstdc++.so.6: cannot handle TLS data

I have an application compiled at:
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Linux debian 2.6.18-5-686 #1 SMP Fri Jun 1 00:47:00 UTC 2007 i686 GNU/Linux
and it runs well.
Now I want to run it at:
Linux 2.4.20_mvlcge31-tomas #7 Thu May 7 11:33:21 CEST 2009 i686 unknown
I got following errors:
libstdc++.so.6: cannot handle TLS data
From the web I saw someone suggested to do this: export LD_ASSUME_KERNEL=2.2.5
I tried but get even more errors:
ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
Who can help me with it? thanks
You had compiled the application against much newer libc and kernel version, You can't compile program on 2.6 with newest libc and expect it to run on old kernel.
Also where do you actually still use Linux 2.4?

Resources