From: chrubis@suse.cz
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18
Date: Mon, 2 Dec 2013 18:52:15 +0100 [thread overview]
Message-ID: <20131202175215.GD15697@rei.suse.cz> (raw)
In-Reply-To: <1385374379-25949-1-git-send-email-markos.chandras@imgtec.com>
Hi!
> 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
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Pushed, thanks.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
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=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-12-02 17:52 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 [this message]
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
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=20131202175215.GD15697@rei.suse.cz \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=markos.chandras@imgtec.com \
/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