public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Michael Hudson-Doyle <michael.hudson@canonical.com>,
	Stan Cox <scox@redhat.com>,
	libc-alpha@sourceware.org, systemtap@sourceware.org,
	Arjun Shankar <ashankar@redhat.com>
Subject: Re: glibc build failure due to Systemtap probe change
Date: Thu, 9 Dec 2021 12:39:02 +0100	[thread overview]
Message-ID: <be759fe2-e540-8790-5af5-8d57ed902aa2@linux.ibm.com> (raw)
In-Reply-To: <87wnkfl7lr.fsf@oldenburg.str.redhat.com>

On 08/12/2021 11:21, Florian Weimer wrote:
> * Stefan Liebler:
> 
>> On 25/11/2021 02:55, Michael Hudson-Doyle wrote:
>>> Hi, On Thu, 18 Nov 2021 at 04:47, Florian Weimer via Libc-alpha
>>> <libc-alpha@sourceware.org> wrote: * Stan Cox: >> Is there a way way to
>>> use STAP_PROBE_ASM without supplying the template? >> There's no type
>>> inspection in ZjQcmQRYFpfptBannerStart
>>> This Message Is From an External Sender
>>> This message came from outside your organization.
>>> ZjQcmQRYFpfptBannerEnd
>>> Hi,
>>>
>>> On Thu, 18 Nov 2021 at 04:47, Florian Weimer via Libc-alpha
>>> <libc-alpha@sourceware.org <mailto:libc-alpha@sourceware.org>> wrote:
>>>
>>>     * Stan Cox:
>>>
>>>     >> Is there a way way to use STAP_PROBE_ASM without supplying the
>>>     template?
>>>     >> There's no type inspection in assembler, after all.
>>>     >
>>>     > Can you send me the failing .i file so I can experiment with it?
>>>
>>>     --save-temps did not work for me for some reason, so I'm attaching -E
>>>     and -E -fdirectives-only output.
>>>
>>>     I think I got Fedora rawhide s390x building again, so it's not *very*
>>>     time-critical, but I really don't want to release Fedora 36 with our own
>>>     private copy of <sys/sdt.h>.  But that release still some months away.
>>>
>>>
>>> Is there any update on this? I just ran into it with my snapshot build
>>> for Ubuntu. I can borrow/steal Florian's fix for now too but I too would
>>> prefer not to release 22.04 with it...
>>>
>>> Cheers,
>>> mwh 
>>
>> As information: This also happens on Fedora 35 with
>> systemtap-sdt-devel-4.6-1.fc35.
> 
> The s390x glibc build should be fixed.
> 
> We are dealing with some other LRA/reload issues due to the probe macro
> changes, but those issues presently do not affect glibc builds on
> Fedora.
> 
> Thanks,
> Florian
> 

I've just updated to systemtap-sdt-devel-4.6-3.fc35 and successfully
build glibc on s390x.

Do you also plan to publish such an update for Fedora 34?

Thanks,
Stefan

  reply	other threads:[~2021-12-09 11:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  9:29 Florian Weimer
2021-11-16 21:52 ` Stan Cox
2021-11-17 10:44   ` Florian Weimer
2021-11-17 13:42     ` Stan Cox
2021-11-17 15:39       ` Florian Weimer
2021-11-25  1:55         ` Michael Hudson-Doyle
2021-11-30 11:13           ` Stefan Liebler
2021-12-08 10:21             ` Florian Weimer
2021-12-09 11:39               ` Stefan Liebler [this message]
2021-12-10 17:44                 ` Frank Ch. Eigler
2021-12-14 13:27                   ` Stefan Liebler
2021-11-18 13:33 ` Stefan Liebler

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=be759fe2-e540-8790-5af5-8d57ed902aa2@linux.ibm.com \
    --to=stli@linux.ibm.com \
    --cc=ashankar@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=michael.hudson@canonical.com \
    --cc=scox@redhat.com \
    --cc=systemtap@sourceware.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).