From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18
Date: Wed, 8 Jan 2014 14:41:42 -0500 [thread overview]
Message-ID: <201401081441.43107.vapier@gentoo.org> (raw)
In-Reply-To: <52CD3B93.8090605@imgtec.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1696 bytes --]
On Wednesday 08 January 2014 06:50:43 Markos Chandras wrote:
> On 01/06/2014 12:49 PM, Mike Frysinger wrote:
> > On Monday 06 January 2014 06:45:43 Markos Chandras wrote:
> >> On 01/05/2014 10:27 PM, Mike Frysinger wrote:
> >>> On Monday 25 November 2013 05:12:59 Markos Chandras wrote:
> >>>> Since glibc-2.18, the struct ptrace_peeksiginfo_args is
> >>>> also defined in sys/ptrace.h and conflicts with the definition
> >>>> from the Linux kernel in linux/ptrace.h. We fix this by not
> >>>> including the linux/ptrace.h header if the sys/ptrace.h header
> >>>> defines the said struct. Fixes
> >>>> https://github.com/linux-test-project/ltp/issues/6
> >>>
> >>> i'm somewhat inclined to undo this as it's really a bug in glibc-2.18
> >>>
> >>> that should be fixed in glibc-2.19:
> >>> https://sourceware.org/ml/libc-alpha/2014-01/msg00078.html
> >>
> >> Ehm that would break the build for people already using 2.18. Even if a
> >> new 2.18 is released with the fix, people using the old one will still
> >> face the same problem.
> >
> > i'm aware that would be the situation. i'm fine with that.
>
> It's not my call to make, but forcing people to update their glibc in
> order to build LTP is a bit too much. I suggest to keep this workaround
> for X months, until more people have been moved to a fixed glibc version.
i'm not forcing people to update their glibc. i am forcing them to get their
distro to land a simple fix. or run a simple sed script as root to fix their
header.
> strace also has similar fix
> http://sourceforge.net/p/strace/code/ci/0b4060f61f1bb101b5d8d084714b7d2feac
> db199/
yes, and i already commented there
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 455 bytes --]
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-01-08 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 10:12 [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18 Markos Chandras
2013-12-02 9:31 ` Markos Chandras
2013-12-02 17:35 ` chrubis
2013-12-02 17:52 ` chrubis
2014-01-05 22:27 ` Mike Frysinger
2014-01-06 11:45 ` Markos Chandras
2014-01-06 12:49 ` Mike Frysinger
2014-01-08 11:50 ` Markos Chandras
2014-01-08 19:41 ` Mike Frysinger [this message]
2014-01-08 15:22 ` chrubis
[not found] ` <201401081442.11349.vapier@gentoo.org>
2014-01-09 11:58 ` chrubis
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=201401081441.43107.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Markos.Chandras@imgtec.com \
--cc=ltp-list@lists.sourceforge.net \
/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