- unixforum.org
- Не устанавливаются пакеты. Проблема предварительных зависимостей
- Не устанавливаются пакеты. Проблема предварительных зависимостей
- Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
- Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
- Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
- Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
- Использование qemu Raspbian: установка libc6: i386 не выполняется
- 1 ответ
- Не удалось настроить libc6 i386
- Solution
- Supported Linux distributions
- Use Synaptic Package Manager (recommended for Trisquel)
- Use Terminal
- Trying to install i386 package libc6:i386 on Raspberry Pi 3 B+ fails
- 2 Answers 2
- Unable to locate package libc6-dev-i386
- 2 Answers 2
unixforum.org
Форум для пользователей UNIX-подобных систем
- Темы без ответов
- Активные темы
- Поиск
- Статус форума
Не устанавливаются пакеты. Проблема предварительных зависимостей
Не устанавливаются пакеты. Проблема предварительных зависимостей
Сообщение imcat » 06.07.2015 10:15
Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
Сообщение Bizdelnick » 06.07.2015 10:31
| в консол и вку́пе (с чем-либо) в общем в ообще | в течени е (часа) нович ок нюанс п о умолчанию | приемл емо пробле ма проб овать тра фик |
Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
Сообщение imcat » 06.07.2015 10:40
Ничего особенно не делал )) Обновилась -и вот теперь вот такое.. apt-get -f install пробовался неоднократно — опять в те же ошибки упирается..
Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
Сообщение Bizdelnick » 06.07.2015 11:55
| в консол и вку́пе (с чем-либо) в общем в ообще | в течени е (часа) нович ок нюанс п о умолчанию | приемл емо пробле ма проб овать тра фик |
Re: Не устанавливаются пакеты. Проблема предварительных зависимостей
Сообщение Rootlexx » 06.07.2015 12:55
Источник
Использование qemu Raspbian: установка libc6: i386 не выполняется
Это мой первый пост на этом форуме.
Я пытаюсь запустить qemu на моем Raspberry Pi 3 с установленным Raspbian stretch. Драйвер сканера My Brother DCP-350C доступен только предварительно скомпилированный для x86. Я добавил арку i386 с помощью sudo dpkg —add-architecture i386 и установил qemu-user binfmt-support. Никаких проблем нет.
Но каждый раз, когда я пытаюсь установить libc6: i386, я получаю сообщение об ошибке установки:
Не знаю, как это исправить. Я перепробовал все виды репозиториев, но, похоже, это не проблема репозитория.
Я больше не знаю, как это исправить.
Я надеюсь, что кто-нибудь может помочь.
1 ответ
Такая ошибка («libgcc1: i386 Breaks: libgcc1 (! = 1: 6.3.0-18), но необходимо установить 1: 6.3.0-18 + rpi1» и «libgcc1: Breaks: libgcc1: i386 (! = 1: 6.3.0-18 + rpi1), но 1: 6.3.0-18 должен быть установлен ») потому, что для поддержки мультиархитектурности в Debian и производных Debian требуется, чтобы все версии пакета для каждой установленной архитектуры имели точно совпадающие версии. Таким образом, вы можете установить вместе libgcc1: i386 1: 6.3.0-18 и libgcc1: armhf 1: 6.3.0-18, потому что версии совпадают, но не libgcc1: i386 1: 6.3.0-18 и libgcc1: armhf 1: 6.3.0-18 + rpi1 (потому что версии точно не совпадают).
Проблема здесь в том, что raspbian перестраивает пакеты, поэтому в конце их версии стоит тег + rpi1. Так что вам понадобится либо
- репозиторий, в котором были собраны версии пакетов raspbian для i386 — этого вполне может не существовать
- или запустите чистый исходный Debian, а не Raspbian, на который вы, вероятно, не захотите переходить на данный момент
- или пересоберите все пакеты для i386 самостоятельно — что, вероятно, будет болезненно и легко ошибиться, если вы не знаете, что делаете.
Если это хоть как-то утешает, я бы в некоторой степени сомневался, сможет ли QEMU с пользой обработать эмуляцию аппаратно-зависимого фрагмента кода, такого как драйвер сканера (который, вероятно, является подключаемым модулем для CUPS или другого системного программного обеспечения).
Источник
Не удалось настроить libc6 i386
This article applies to an ESET product version that is currently in Limited Support status and is scheduled to reach End of Life status soon.
For a complete list of supported products and support level definitions, review the ESET End of Life Policy for home products.
- Installation error «ESET NOD32 for Linux needs the following packages to install: libc6-i386, /lib/ld-linux.so.2»
- Use Synaptic Package Manager (recommended for Trisquel)
- Use Terminal
Solution
When installing ESET NOD32 Antivirus for Linux Desktop, you may receive the error «ESET NOD32 for Linux needs the following packages to install: libc6-i386, /lib/ld-linux.so.2 » on unsupported versions of Ubuntu (13.04+) and 64-bit Trisquel with Gnome. To resolve this issue, follow the instructions in one of the methods below.
Supported Linux distributions
The Linux distributions supported by ESET NOD32 Antivirus 4 for Linux Desktop are as follows: Red Hat, Mandriva, SUSE, Debian, Ubuntu (up to Ubuntu 12.10), and Fedora (32-bit). Installing on other Linux distributions may require the administrator to perform additional tasks due to the large variety of Linux distributions. These tasks may include the installation of missing packages or init script modification.
Use Synaptic Package Manager (recommended for Trisquel)
Open a Terminal window and run the following command:
In the Software & Updates window, click Updates.
Select the check box next to Recommended updates (trusty-updates), type in your administrator password when prompted and then click Close.
Figure 1-1
- Click Reload when you are asked to update the list of available software–you must have an internet connection to continue.
Figure 1-2
Run the following command:
sudo apt-get install libc6 -i386
Use Terminal
Open a Terminal window and run the following commands:
sudo apt-get update
Run the following command. You can use your mouse to copy the commands in the video to paste into your Terminal.
sudo apt-get upgrade
Restart your system.
Run the following command. You can use your mouse to copy the commands in the video to paste into your Terminal.
Источник
Trying to install i386 package libc6:i386 on Raspberry Pi 3 B+ fails
The end goal is to get my Raspberry Pi to work as a print server providing AirPrint for a Brother DCP-195C printer they already have.
So I already got to the point of where I installed the printer driver, but since that is only provided in compiled form for 32bit x86. So I tried to install Qemu to be able to use those.
I’m getting stuck on
A bit more information:
2 Answers 2
I managed to make the DCP-197C to work:
I don’t know if I miss something, because I tried it so many times, but I want to write somewhere what I did today, when it finally worked:
Install all the necessary stuff
Download libc6 for i386 (I found it here)
If you try to install this, you will mess around with apt, so we will extract the deb and copy these files manually
Run this and add it to bashrc to run in every reboot
Download and install your drivers — for me e.g.:
I’m having the very same issue. From what I can tell there is not really a way to fix it at the moment. libc6:armhf can be installed alongside the i386 version if they are the exact same version. Because however, all raspbian packages have «rpi#» (# will be your version of the pi, so e.g. 1 for rpi 1/zero, 2 for 2 etc.) added into their version number, the versions will never line up correctly. This basically means that i386 can’t be installed on raspbian (I have literally no idea how the guy from the post you referenced got it working).
I have found this post on a German forum saying that multiarch is working properly on Ubuntu Mate (which, unfortunately for me isn’t available for RPi 1 and Zero) so it might be worth a shot to try this whole thing through Ubuntu.
Источник
Unable to locate package libc6-dev-i386
I’m trying to install NS3, and got stuck at this package, libc6-dev-i386, installation.
I’ve tried all the possible solution that i can find on the google, so far.
I’ve tried direct command,
sudo apt install libc6-dev-i386
sudo dpkg —add-architecture i386 , and then try to run the update command.
But again no luck, and i think this attempt is stupid coz my base architecture is i386, so i don’t need to add it(can anybody confirm), but i tried it any way.
sudo apt install -f , even though i don’t know what -f stands for.
I’ve also read that this package automatically installed with g++, and I’ve g++ 6.3.0.
I get the same error after all of those tries:
I’m not getting, locate where, in the website?
EDIT
The o/p of, lsb_release -a.,
and, that «s» at the end of «architecture», is my bad. I was trying the foreign command.
2 Answers 2
The development library libc6-dev-i386 is only necessary for developing 32-bit software in a 64-bit OS.
According to the results posted (pending confirmation) the OS is 32-bit (i386) therefore it doesn’t require the said library and the library isn’t available in the repositories (it is available for 64-bit Ubuntu only).
The installation can proceed without it.
On 32-bit Ubuntu, skip that package. Just install libc6-dev and whatever other packages you need.
The specific package that corresponds to libc6-dev-i386 for a 32-bit system is just libc6-dev , which you are already installing.
There is no libc6-dev-i386 package for your system, because it’s only available on 64-bit systems. This, in turn, is because its purpose is to provide you with the ability to build and run 32-bit programs on a 64-bit system.
Ubuntu supports several architectures. For PCs, meaning most desktops and laptops, including those manufactured by Apple in recent years, there are two: i386 for 32-bit systems and amd64 for 64-bit systems. For the rest of this answer when I say «32-bit» and «64-bit» I am referring to those architectures specifically. (These confusingly named architectures have important differences, hardware may support both or just i386 though you may need the amd64 version on UEFI systems, and you can check the architecture of your machine or Ubuntu installation.)
64-bit processors are capable of running both 64-bit and 32-bit native (machine language) code.
- If you have the 64-bit (amd64) version of Ubuntu, you can automatically run 64-bit programs.
- You can also run 32-bit programs, but you may need to install 32-bit support libraries, including the 32-bit version of libc6 .
To run, most programs require the libraries provided by the libc6 package. Ubuntu has this package installed already. Like most (but not all) packages in Ubuntu, the libc6 package is provided separately for different architectures.
To create an executable that links to the libraries provided by libc6 , you need to have the header files for that library. Those are provided by the libc6-dev package. The libc6-dev package also declares the libc6 package as a dependency, because it would not usually be useful to have just the header files but not the library itself. Most -dev packages declare some corresponding non- -dev package as a dependency.
Because the vast majority of programs require libc6 directly or indirectly, more than one way to install the 32-bit version of this library and its header files on a 64-bit system has been provided over the years.
- The most general way, which works with almost every other library as well, is to use APT’s multiarch support—multiarch is enabled by default on all recent Debian and Ubuntu systems—by running dpkg —add-architecture i386 and using apt or apt-get to install the libc6:i386 and libc6-dev:i386 packages. apt and apt-get support specifying the architecture of a package to install using this : syntax.
- However, there are other ways. The 32-bit ( i386 ) versions of some commonly needed libraries are provided as special amd64 -only packages. libc6-i386 and libc6-dev-i386 are two such packages. The libc6-dev-i386 package provides the 32-bit versions of header files that differ between architectures while declaring as dependencies libc6-dev , which is sufficient for the others, and libc6-i386 , which provides the actual 32-bit libraries.
- The old way to install common 32-bit libraries on a 64-bit system was with the ia32-libs package.
Based on the commands you ran, it seems like you tried both of the first two methods, or a combination of the two. However, your system neither requires nor is capable of either, since it’s a 32-bit system. 32-bit systems don’t need anything special to be able to run 32-bit programs (and they cannot run 64-bit programs).
Источник