Toolchain install problem (gcc-arm-embedded)?

the Toolchain Setup as descibed in your documentation seems to cause a problem on Ubuntu 18.04 (latest) wgen other gcc Toolchains are installed. I receive the following error message:
sudo apt install gcc-arm-embedded
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following additional packages will be installed:
The following NEW packages will be installed:
gcc-arm-embedded libisl15
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 69,4 MB of archives.
After this operation, 453 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 bionic/universe amd64 libisl15 amd64 0.18-4 [548 kB]
Get:2 bionic/main amd64 gcc-arm-embedded amd64 7-2018q2-1~bionic1 [68,9 MB]
Fetched 69,4 MB in 41s (1.680 kB/s)
Selecting previously unselected package libisl15:amd64.
(Reading database … 222471 files and directories currently installed.)
Preparing to unpack …/libisl15_0.18-4_amd64.deb …
Unpacking libisl15:amd64 (0.18-4) …
Selecting previously unselected package gcc-arm-embedded.
Preparing to unpack …/gcc-arm-embedded_7-2018q2-1~bionic1_amd64.deb …
Unpacking gcc-arm-embedded (7-2018q2-1~bionic1) …
dpkg: error processing archive /var/cache/apt/archives/gcc-arm-embedded_7-2018q2-1~bionic1_amd64.deb (–unpack):
trying to overwrite ‘/usr/lib/’, which is also in package gcc-avr 1:5.4.0+Atmel3.6.0-1build1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

I’m developing with various microcontrollers. Do you have an idea on how to fix this?


based on the output the conflict is with some library that is used with gcc-avr. We do not use AVRs so nobody in our team will know the answer.

I’we found something on google, take a look if you google:‘’%2C+which+is+also+in+package+gcc-avr+1%3A5.4.0%2BAtmel3.6.0-1build1&oq=trying+to+overwrite+‘’%2C+which+is+also+in+package+gcc-avr+1%3A5.4.0%2BAtmel3.6.0-1build1&aqs=chrome..69i57.679j0j7&sourceid=chrome&ie=UTF-8

Hi Martin,
hmmm, it’s a bug. :weary:

Thanks for help.

BR Peter