Linux-RDMA Archive on lore.kernel.org
 help / color / Atom feed
From: Gal Pressman <galpress@amazon.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>
Subject: Re: Can't build rdma-core's azp image
Date: Thu, 16 Apr 2020 10:05:11 +0300
Message-ID: <ca41331c-3b53-fbb6-4543-bc960f796062@amazon.com> (raw)
In-Reply-To: <67f9e08a-467c-34ce-e17e-816cb4bf03db@amazon.com>

On 08/04/2020 9:35, Gal Pressman wrote:
> On 07/04/2020 21:06, Jason Gunthorpe wrote:
>> On Tue, Apr 07, 2020 at 06:47:51PM +0300, Gal Pressman wrote:
>>> I'm trying to build the azp image and it fails with the following error [1].
>>> Anyone has an idea what went wrong?
>>
>>> Reading package lists...
>>> W: http://apt.llvm.org/bionic/dists/llvm-toolchain-bionic-8/InRelease: No system
>>> certificates available. Try installing ca-certificates.
>>> W: http://apt.llvm.org/bionic/dists/llvm-toolchain-bionic-8/Release: No system
>>> certificates available. Try installing ca-certificates.
>>> E: The repository 'http://apt.llvm.org/bionic llvm-toolchain-bionic-8 Release'
>>> does not have a Release file.
>>
>> Oh, there is lots going wrong here..
>>
>> Above is because llvm droped http support from their repo.. Bit
>> annoying to fix..
>>
>>> The following packages have unmet dependencies:
>>>  libc6-dev:arm64 : Depends: libc6:arm64 (= 2.27-3ubuntu1) but it is not going to
>>> be installed
>>>  libgcc-8-dev:arm64 : Depends: libgcc1:arm64 (>= 1:8.4.0-1ubuntu1~18.04)
>>>                       Depends: libgomp1:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>                       Depends: libitm1:arm64 (>= 8.4.0-1ubuntu1~18.04) but it is
>>> not going to be installed
>>>                       Depends: libatomic1:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>                       Depends: libasan5:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>                       Depends: liblsan0:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>                       Depends: libtsan0:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>                       Depends: libubsan1:arm64 (>= 8.4.0-1ubuntu1~18.04) but it
>>> is not going to be installed
>>>  libnl-3-dev:arm64 : Depends: libnl-3-200:arm64 (= 3.2.29-0ubuntu3) but it is
>>> not going to be installed
>>>  libnl-route-3-dev:arm64 : Depends: libnl-route-3-200:arm64 (= 3.2.29-0ubuntu3)
>>> but it is not going to be installed
>>>  libsystemd-dev:arm64 : Depends: libsystemd0:arm64 (= 237-3ubuntu10.39) but it
>>> is not going to be installed
>>>  libudev-dev:arm64 : Depends: libudev1:arm64 (= 237-3ubuntu10.39) but it is not
>>> going to be installed
>>
>> Oh neat, that is a problem in the toolchain ppa:
>>
>> $ apt-get install libgcc-s1:arm64 gcc-7
>>
>> The following packages have unmet dependencies:
>>  libgcc-s1:arm64 : Breaks: libgcc-7-dev (< 7.5.0-4) but 7.5.0-3ubuntu1~18.04 is to be installed
>>
>> The only ubuntu not broken right now is focal.. which is very new.
>>
>> Keep using the old docker image? Ask me in a week if it is still
>> broken, we can probably fix this by updating to focal, it is the next
>> LTS anyhow..
> 
> Thanks Jason, I'll keep tracking the issue.

Looks like the issue persists :\.

  reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 15:47 Gal Pressman
2020-04-07 17:28 ` Leon Romanovsky
2020-04-07 18:06 ` Jason Gunthorpe
2020-04-08  6:35   ` Gal Pressman
2020-04-16  7:05     ` Gal Pressman [this message]
2020-04-17 16:21       ` Jason Gunthorpe
2020-04-19  6:37         ` Gal Pressman
2020-05-05  1:09           ` Jason Gunthorpe
2020-05-05  6:40             ` Gal Pressman
2020-05-05 13:21               ` Jason Gunthorpe
2020-05-05 14:05                 ` Gal Pressman
2020-05-26  6:25 ` Gal Pressman
2020-05-26 19:23   ` Jason Gunthorpe
2020-05-27  7:35     ` Gal Pressman
2020-07-26  7:05       ` Gal Pressman
2020-07-26 23:19         ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ca41331c-3b53-fbb6-4543-bc960f796062@amazon.com \
    --to=galpress@amazon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-RDMA Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-rdma/0 linux-rdma/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rdma linux-rdma/ https://lore.kernel.org/linux-rdma \
		linux-rdma@vger.kernel.org
	public-inbox-index linux-rdma

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-rdma


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git