Sergey Baigudin

Уверен, что поддержать NXP S32Gx - это было бы замечательно.

Спасибо большое! Сейчас попробовал на своей хостовой Ubuntu 22.04 - KOS SDK установилось, пример "hello world" собрался и под QEMU запустился. Вероятно можно на ней и работать. Но переписку всё равно оставлю открытой, хочется услышать ответ коллег из Касперского, как они это на Debian 10.12 делают.

Успешно установил KOS SDK в Docker. После решил, что удобнее будет разрабатывать на хостовой системе Debian 10.12, как указано в документации. Установил Debian 10.12 (AMD64) под VirtualBox. В /etc/apt/sources.list прописал следующие источники: deb http://security.debian.org/debian-security buster/updates main contrib deb-src http://security.debian.org/debian-security buster/updates main contrib deb http://deb.debian.org/debian stretch main deb-src http://deb.debian.org/debian stretch main После выполнил установку DEB пакета и получил следующую ошибку: $ sudo apt update $ sudo apt install ./KasperskyOS-Community-Edition_1.1.1.13_en.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'kasperskyos-community-edition' instead of './KasperskyOS-Community-Edition_1.1.1.13_en.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: kasperskyos-community-edition : Depends: flex (>= 2.6.4) but it is not going to be installed Depends: doxygen but it is not going to be installed E: Unable to correct problems, you have held broken packages. После, для начала, установил flex: $ sudo apt install flex $ flex --version flex 2.6.1 И повторил попытку установки DEB пакета KOS SDK: $ sudo apt install ./KasperskyOS-Community-Edition_1.1.1.13_en.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'kasperskyos-community-edition' instead of './KasperskyOS-Community-Edition_1.1.1.13_en.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: kasperskyos-community-edition : Depends: flex (>= 2.6.4) but 2.6.1-1.3 is to be installed Depends: doxygen but it is not going to be installed E: Unable to correct problems, you have held broken packages. То есть я правильно понимаю, что сейчас мне надо каким-то образом "ручками" поставить именно flex 2.6.4 вместо хостового 2.6.1? Далее я решил попробовать "вылечить" зависимость на Doxygen: $ sudo apt install doxygen Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: doxygen : Depends: libclang1-3.9 (>= 1:3.9.1-6~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. И тоже получил ошибку зависимостей. Коллеги, Касперский, скажите, а есть какие-то инструкции, чтобы настроить среду разработки и установки SDK на "голой" Debian 10.12, тем более, что она явно и безальтернативно фигурирует в документации на KOS SDK CE 1.1.1?

Спасибо! Что-то я не подумал. Проверил, работает. Да, тогда думаю коллегам возможно стоит тут в инструкции написать так: $ apt update $ apt install <путь-к-deb-пакету> что-бы было очевиднее таким, как я ?

Доброго времени суток, коллеги. Устанавливаю KOS SDK в Docker-контейнере Debian:10.12 следуя инструкции. Столкнулся со следующей проблемой как для CE 1.1.1.13, так и для CE 1.1.0.24: # apt install ./KasperskyOS-Community-Edition_1.1.1.13_en.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'kasperskyos-community-edition' instead of './KasperskyOS-Community-Edition_1.1.1.13_en.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: kasperskyos-community-edition : Depends: make (>= 3.81) but it is not installable Depends: flex (>= 2.6.4) but it is not installable Depends: libasound2 (>= 1.0.16) but it is not installable Depends: libglib2.0-0 (>= 2.24.0) but it is not installable Depends: libncurses5 (>= 5.5-5~) but it is not installable Depends: libpulse0 (>= 0.99.1) but it is not installable Depends: libtinfo5 but it is not installable Depends: libx11-6 but it is not installable Depends: libpython2.7 (>= 2.7) but it is not installable Depends: socat (>= 1.7) but it is not installable Depends: cpp but it is not installable Depends: parted (>= 3.2-25) but it is not installable Depends: libpng16-16 (>= 1.6.28-1) but it is not installable Depends: device-tree-compiler but it is not installable Depends: sudo but it is not installable Depends: build-essential (>= 12.4) but it is not installable Depends: libsdl2-2.0-0 (>= 2.0.2) but it is not installable Depends: libusb-1.0-0 but it is not installable Depends: libpixman-1-0 but it is not installable Depends: libcurl3-gnutls (>= 7.38) but it is not installable Depends: doxygen but it is not installable Depends: dosfstools but it is not installable E: Unable to correct problems, you have held broken packages. Для её решения необходимо установить make: # apt-get update # apt-get -y install make # make --version GNU Make 4.2.1 Возможно установку make нужно включить в SDK или описать данную проблему в документации.