Gentoo Archives: gentoo-soc

From: wuyy <xgreenlandforwyy@×××××.com>
To: gentoo-soc@l.g.o
Subject: Re: [gentoo-soc] Week 1 Report for Refining ROCm Packages in Gentoo
Date: Tue, 21 Jun 2022 09:14:40
Message-Id: YrGMB2O4BCenWOLO@HEPwuyy
In Reply to: Re: [gentoo-soc] Week 1 Report for Refining ROCm Packages in Gentoo by Benda Xu
1 On Tue, Jun 21, 2022 at 04:35:20PM +0800, Benda Xu wrote:
2 > > Benda Xu <heroxbd@g.o> writes:
3 >
4 > You are not answering my question. My original comment was only on the
5 > severe issue of hipcc 'isystem'. Although you mentioned "I came to a
6 > new hipvars.pm and a patch to hipcc.pl, disabling poisoning `-isystem`
7 > and correcting many paths", I cannot see any fix pushed into ::gentoo.
8 > Otherwise we won't be bitten by bug 853184.
9
10 The statement "I came to a new hipvars.pm and a patch to hipcc.pl,
11 disabling poisoning `-isystem`" describes the situation in packaging
12 dev-util/hip-5.1.3 against vanilla llvm/clang on my own development
13 branch, and it is independent of ug 853184 (they may share some
14 similarities, but at that time I didn't realize there can be bug in
15 hip-5.0.2). Bug 853184 is introduced by https://github.com/gentoo/gentoo/pull/25861.
16
17 I am sorry for pusin dev-util/hip-5.0.2-r1 without test it's functionality.
18 I'll go back to the 5.0.2 branch and fix up the mess, and setup a CI
19 system to provide solid testings.
20
21 >
22 > This is a situation you should avoid at all cost in the future.
23
24 --