From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7D964393D01C; Fri, 14 May 2021 07:57:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D964393D01C From: "tbaeder at redhat dot com" To: systemtap@sourceware.org Subject: [Bug server/26839] Systemtap build failures with clang Date: Fri, 14 May 2021 07:57:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: server X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tbaeder at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: systemtap@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Systemtap mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2021 07:57:58 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26839 --- Comment #10 from Timm B=C3=A4der --- (In reply to Aaron Merey from comment #9) > (In reply to Timm B=C3=A4der from comment #8) > > Hey Frank do you have any update on this? We've been carrying the patch= es > > around for a while now and they need maintenance and start to collide w= ith > > upstream changes, e.g. > > https://sourceware.org/git/?p=3Dsystemtap.git;a=3Dcommit; > > h=3D439fb4cc4c08166dccb85ba202a5762c4c46ba42 > >=20 > > I think only the probe::printsig() problems need clarification, the oth= er > > ones are straight forward. >=20 > Hi Timm. When I merged that commit I didn't realise you had a similar pat= ch > pending. Regarding the printsig patch, I would suggest dropping the 'bool > nest =3D true' definitions and instead call printsig_nested unconditional= ly. No problem, in the end it's one patch less we carry around. Dropping the ne= st bool is fine with me of course, I have a patch doing that. I can't seem to = find where to send patches however, the mailing list seems to have remarkably fe= w of them and the HACKING document doesn't seem to mention? Where does systemtap development happen? > Otherwise the patch set looks ok. With it, gcc still compiles systemtap > without error and we are closer to being able to compile systemtap with > clang. I still get an errors when compiling with clang however. ex. > `unsupported argument 'auto' to option 'flto=3D'` when compiling > systemtap/python/HelperSDT/_HelperSDT.c I can't seem to find where -flto=3Dauto could come from within the systemtap sources, is that in your env somehow? That shouldn't be used when compiling with clang. If you need a workaround, setting CCC_OVERRIDE_OPTIONS=3D"x-flto=3Dauto" should work. Later versions of clang will also ignore -flto=3Dauto: https://github.com/llvm/llvm-project/commit/1628486548420f85b3467026d54663d= 1516404f5 --=20 You are receiving this mail because: You are the assignee for the bug.=