I'm using
Linux archbios 5.13.6-arch1-1 #1 SMP PREEMPT Thu, 29 Jul 2021 00:21:06 +0000 x86_64 GNU/Linux
operating system.
My problem comes after following the sublime official instructions for Arch. After these steps from sublime official docs, I just need to upgrade the sublime
sudo pacman -Syu sublime-text
I don't understand from where comes this error
sudo pacman -Syu sublime-text
:: Synchronizing package databases...
core 136.1 KiB 340 KiB/s 00:00 [##########################] 100%
extra 1566.4 KiB 3.00 MiB/s 00:01 [##########################] 100%
community 5.6 MiB 3.16 MiB/s 00:02 [##########################] 100%
multilib 149.8 KiB 1248 KiB/s 00:00 [##########################] 100%
sublime-text is up to date
:: Starting full system upgrade...
error: failed to prepare transaction (package architecture is not valid)
:: package sublime-text-4113-1-aarch64 does not have a valid architecture
I've checked /etc/pacman.conf
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
[sublime-text]
Server = https://download.sublimetext.com/arch/stable/x86_64
Not quit sure, maybe problem is that when you type
pacman -Syu sublime-text // it takes default version for "sublime-text-4113-1-aarch64
but with yay and mention from where works,
yay -S aur/sublime-text-4
with this command it just works
I think I pasted the wrong version into the commandline and now have aarch64 errors also.
Removed the URL reference to aarch64 in the pacman.conf file which fixed half the problem.
Moved the var/lib/pacman/sync files into a backup directory. Re-ran the command:
sudo pacman -Syu sublime-text
FINALLY worked.
I can confirm Lord High Fixer's solution worked for me as well. I accidentally picked the wrong channel for aarch64 at first, then even after removing that channel from /etc/pacman.conf, I would continue getting the "package sublime-text-4113-1-aarch64 does not have a valid architecture" error.
I created a 'backup folder' in /var/lib/pacman/sync and moved sublime-text.db and sublime-text.db.sig into the folder. Ran pacman -Syu sublime-text and it installed correctly.
Related
trying to compile openmpi with intel oneapi 2022.0.1 compilers
OS is 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I got the intel compilers as follows (just to make sure I didn't mess anything up at that step)
sudo add-apt-repository "deb https://apt.repos.intel.com/oneapi all main"
sudo apt install intel-basekit
sudo apt install intel-hpckit
Configuring openmpi with:
./configure --prefix=${HPCX_HOME}/ompi-icc CC=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/icc CXX=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/icpc F77=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/ifort FC=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/ifort --with-ucx=/usr --with-platform=contrib/platform/mellanox/optimized
my .bashrc has (root has the same .bashrc)
source /opt/intel/oneapi/setvars.sh
export LD_LIBRARY_PATH=/opt/intel/oneapi/compiler/2022.0.1/linux/compiler/lib/intel64_lin
After configure I do : sudo make all install and get the following error:
ld: /opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/../../bin/intel64/../../lib/icx-lto.so: error loading plugin: libimf.so: cannot open shared object file: No such file or directory
There is no ifortvars.sh with this new version of oneAPI which seems to have solved similar issues for others in the past.
libimf.so is in:
/opt/intel/oneapi/itac/2021.5.0/bin/rtlib/libimf.so
/opt/intel/oneapi/compiler/2022.0.1/linux/compiler/lib/intel64_lin/libimf.so
/opt/intel/oneapi/intelpython/python3.9/pkgs/intel-cmplr-lib-rt-2022.0.1-intel_3633/lib/libimf.so
/opt/intel/oneapi/intelpython/python3.9/lib/libimf.so
/opt/intel/oneapi/intelpython/python3.9/envs/2022.0.1/lib/libimf.so
Any help and/or advice regarding compiling openmpi with recent intel compilers would be appreciated.
Here is the solution I found but doubt that this is the most elegant way of doing this:
OS is 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
my .bashrc has (root has the same .bashrc)
source /opt/intel/oneapi/setvars.sh
created intel_libs.conf in
/etc/ld.so.conf.d/ and added the line /opt/intel/oneapi/compiler/2022.0.1/linux/compiler/lib/intel64_lin this is where the libimf.so lives.
sudo ldconfig
compiled openmpi with intel compilers fine after that using:
./configure --prefix={HPCX_HOME}/ompi-icc CC=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/icc CXX=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/icpc F77=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/ifort FC=/opt/intel/oneapi/compiler/2022.0.1/linux/bin/intel64/ifort --with-ucx=/usr --with-platform=contrib/platform/mellanox/optimized
sudo make all
sudo make install
I hope this helps someone else and please let me know if there is a better way of doing this. Cheers
I am also facing similar issue not exactly. I installed the new ifort using the following command lines:
wget https://registrationcenter-download.intel.com/akdlm/irc_nas/18236/l_BaseKit_p_2021.4.0.3422.sh
sudo bash l_BaseKit_p_2021.4.0.3422.sh
wget https://registrationcenter-download.intel.com/akdlm/irc_nas/18211/l_HPCKit_p_2021.4.0.3347.sh
sudo bash l_HPCKit_p_2021.4.0.3347.sh
There is no file called setvars.sh inside the source /opt/intel/oneapi/, also while compiling any mpiifort file it is throwing me an error saying:
error loading plugin: libimf.so: cannot open shared object file: No such file or directory
Not even sure, if this is related to this thread or not, but any further guidance would be very helpful, thanks in advance.
I have installed and used screen many times on several different operating systems. Recently I installed it on a NetBSD-8.0 virtual machine.
$ sudo pkgin install screen
calculating dependencies...done.
1 package to install:
screen-4.8.0nb1
0 to refresh, 0 to upgrade, 1 to install
0B to download, 1098K to install
proceed ? [Y/n] Y
installing screen-4.8.0nb1...
screen-4.8.0nb1: setting permissions on /usr/pkg/bin/screen-4.8.0 (o=root, g=wheel, m=4511)
screen-4.8.0nb1: adding /usr/pkg/bin/screen to /etc/shells
screen-4.8.0nb1: registering info file /usr/pkg/info/screen.info
===========================================================================
$NetBSD: MESSAGE,v 1.5 2005/12/28 17:53:24 reed Exp $
[snip]
===========================================================================
pkg_install warnings: 0, errors: 0
reading local summary...
processing local summary...
marking screen-4.8.0nb1 as non auto-removable
However, when I went to use it, I got an immediate failure.
$ uname -mrs
NetBSD 8.0 amd64
$ ls -l /usr/pkg/bin/screen
lrwxr-xr-x 1 root wheel 12 Apr 6 02:50 /usr/pkg/bin/screen -> screen-4.8.0
$ groups
users wheel
$ screen
poll: Invalid argument
This problem persists even when I first remove, then reinstall the screen package. Any suggestions as to what's wrong?
My guess is that the system used to build binary packages for 8.0 (as of the 8.0_2020Q1 pkgsrc release) is no longer quite compatible with the NetBSD-8.0 release. It is likely running on a newer release, inside a chroot(8) sandbox.
I would recommend using NetBSD-9.0 instead, as that is the latest NetBSD release, or NetBSD-8.2, as that is the latest release in the netbsd-8 branch. Using the latest NetBSD and pkgsrc releases provides better coverage against unpatched vulnerabilities.
However, if you want to keep using NetBSD-8.0, you can get a working screen(1) from the 8.0_2019Q4 pkgsrc release. To have pkgin(1) pull from that release, edit the /usr/pkg/etc/pkgin/repositories.conf file to use this repository URL:
http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0_2019Q4/All
There is currently likely just one line in the file that is not commented out, and it points to a URL with just 8.0 in it (which on the server is a symbolic link to the latest pkgsrc release). Just replace that line, or comment it out and add the above line.
Then remove and re-install screen:
sudo pkgin remove screen && sudo pkgin install screen
Hello everybody,
I try to install the Yocto toolchain with Qt5 to cross-compile code for my Gumstix Overo board on my ubuntu 16.04 virtual machin.
I successfully passed the first step of build with bitbake core-image-sato there but now I need to pass the Qt5 build with bitbake meta-toolchain-qt5 and that is my problem.
That is the error:
ERROR: meta-toolchain-qt5-1.0-r0 do_populate_sdk: Could not invoke dnf. Command '/home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/sdk/image/etc/dnf/dnf.conf --setopt=reposdir=/home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/sdk/image/etc/yum.repos.d --repofrompath=oe-repo,/home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/oe-sdk-repo --installroot=/home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/sdk/image --setopt=logdir=/home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/temp --nogpgcheck install nativesdk-packagegroup-sdk-host packagegroup-cross-canadian-overo nativesdk-packagegroup-qt5-toolchain-host' returned 1:
Added oe-repo repo from /home/bschneider/overo/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/meta-toolchain-qt5/1.0-r0/oe-sdk-repo
Last metadata expiration check: 0:00:01 ago on Fri 01 Jun 2018 02:46:23 PM UTC.
That is the all result:
bitbucket link
Someone can please help me to solve this problem. I tried many times to build that but now I have no more idee how to fix it.
Thanks you.
I think you need to backport this patch from upstream meta-qt5
#Khem, I tried to replace my nativesdk-qtbase_git.bb by your proposal but that have only created an compatibility error....
Finaly I found a solution that is proposed in the second link that is in the patch there. I replace the PACKAGE_CLASSES ?= "package_rpm" by PACKAGE_CLASSES ?= "package_ipk" in the local.conf file.
After that I recompile the toolchain with bitbacke meta-toolchain-qt5 and that works.
Thank you.
I have problem installin passenger under Linux.
The way I'm doning it is
Added repository: deb https://oss-binaries.phusionpassenger.com/apt/passenger trusty main to /etc/apt/sources.list.d/passenger.list
Installed it:
sudo apt-get install libapache2-mod-passenger
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libev4
Use 'apt-get autoremove' to remove it.
The following NEW packages will be installed:
libapache2-mod-passenger
0 upgraded, 1 newly installed, 0 to remove and 580 not upgraded.
Need to get 0 B/273 kB of archives.
After this operation, 1 281 kB of additional disk space will be used.
Selecting previously unselected package libapache2-mod-passenger.
(Reading database ... 287776 files and directories currently installed.)
Preparing to unpack .../libapache2-mod-passenger_1%3a5.0.13-1~trusty1_amd64.deb ...
Unpacking libapache2-mod-passenger (1:5.0.13-1~trusty1) ...
Setting up libapache2-mod-passenger (1:5.0.13-1~trusty1) ...
Then I tried to enable passenger module with sudo a2enmod passenger but for some reason I had /etc/apache2/mods-available/passenger.conf and /etc/apache2/mods-available/passenger.load files missed after installation. (They are not created and also not removed with libapache2-mod-passenger so I suppose this is some kind of a bug). So I created them manually:
s
set#set:~$ which ruby
/home/set/.rvm/rubies/ruby-2.1.5/bin/ruby
set#set:~$ which rails
/home/set/.rvm/gems/ruby-2.1.5/bin/rails
set#set:~$ ll /usr/lib/apache2/modules/ | grep passenger
-rw-r--r-- 1 root root 1209112 Jul 3 01:35 mod_passenger.so
/etc/apache2/mods-available/passenger.conf:
<IfModule passenger_module>
PassengerRoot /home/set/.rvm/gems/ruby-2.1.5/bin/passenger
PassengerRuby /home/set/.rvm/rubies/ruby-2.1.5/bin/ruby
</IfModule>
and /etc/apache2/mods-available/passenger.load:
LoadModule passenger_module /usr/lib/apache2/modules/mod_passenger.so
the module was successfully enabled then but when I was restarting apache it throw me a segfault:
a
Starting web server apache2 Segmentation fault (core dumped)
Action 'start' failed.
The Apache error log may have more information.
The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
and the coredump:
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from apache2...(no debugging symbols found)...done.
[New LWP 30116]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/apache2 -k start'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007faa58b8e37e in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_begin() const () from /usr/lib/apache2/modules/mod_passenger.so
So I stuck at this point and have no idea where to move nex. Reinstalling of libapache2-mod-passenger does not help. How can I fix this problem?
This issue is more like memory issue.
I am facing something similar as your issue. But my case is happening with the virtual box VM's. A similar setup for me worked on a typical hardware with more RAM.
What I am doing now to fix this issue is to install the latest passenger module.
gem install passenger and running passenger-install-apache2-module which comes natively with passenger.
and I think the latest module just work.
Here is my puppetmaster.conf file entries under apache conf dir.
LoadModule passenger_module /usr/local/share/gems/gems/passenger-5.0.26/buildout/apache2/mod_passenger.so
PassengerRoot /usr/local/share/gems/gems/passenger-5.0.26
I'm trying to compile the latest stable (2.8.19) version of Redis. Build is successfull as well as all tests, but unexpectedly server runs on 32bit arch.
Log entries:
# Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Redis 2.8.19 (00000000/0) 32 bit
Running in stand alone mode
Port: 6582
PID: 2381
Redis-cli INFO display arch_bits:32. Previous instance (version 2.4.6) works well on arch_bits 64, but I don't know which way it was installed.
OS version info:
root:~# uname -a
Linux localhost 2.6.32-5-amd64 #1 SMP Tue Mar 8 22:49:26 UTC 2011 x86_64 GNU/Linux
root:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.1 (squeeze)
Release: 6.0.1
Codename: squeeze
root:~# arch
x86_64
What are the ways to fix this issue and run latest redis as 64bit?
UPD
Despite above commands output, dpkg --print-architecture returns i386 and all packages in system are all or i386. Only redis-server 2.4.*, installed as a package, is strangely ia64.
What can I do in this situation? The server was setup long time ago by another person, and I is still too newbie in Unix.
It seems, my server needs a full migration from 32 to 64-bit architeture.
Current task solved by downloading compiled 64-bit DEB-package and installing it manually.