From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] probe syscall.* fails with compilation error
Date: Tue, 06 May 2014 18:17:00 -0000 [thread overview]
Message-ID: <bug-16914-6586-e88pt9PU6n@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16914-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16914
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #4 from Josh Stone <jistone at redhat dot com> ---
(In reply to Martin Cermak from comment #0)
> kernel-3.13.0-0.rc7.31.sa2.bz1094366.aarch64 (3.13.0-0.rc7.31 + rhbz1094366 fix)
This kernel does have CONFIG_COMPAT=y, but I don't think that's typical for
that product. Regardless, we need to be prepared for the possibility.
(In reply to Martin Cermak from comment #3)
> (In reply to David Smith from comment #2)
> > Does aarch64 run 32-bit executables?
> My *guess* is that it doesn't. Certainly gcc doesn't support -m32.
The architecture does support 32-bit, but distros might choose not to enable it
in the kernel or toolchain.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-06 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:00 [Bug translator/16914] New: " mcermak at redhat dot com
2014-05-06 14:00 ` [Bug translator/16914] " mcermak at redhat dot com
2014-05-06 14:30 ` dsmith at redhat dot com
2014-05-06 17:46 ` mcermak at redhat dot com
2014-05-06 18:17 ` jistone at redhat dot com [this message]
2014-05-06 18:36 ` dsmith at redhat dot com
2014-05-06 19:42 ` mcermak at redhat dot com
2014-05-06 20:05 ` dsmith at redhat dot com
2014-05-06 20:23 ` mcermak at redhat dot com
2014-05-06 20:44 ` dsmith at redhat dot com
2015-02-12 16:36 ` aram.h at mgk dot ro
2015-02-12 17:34 ` dsmith at redhat dot com
2015-02-12 18:18 ` aram.h at mgk dot ro
2015-02-12 19:07 ` dsmith at redhat dot com
2015-02-12 21:10 ` aram.h at mgk dot ro
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=bug-16914-6586-e88pt9PU6n@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).