public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Mike Frysinger <vapier@gentoo.org>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18
Date: Mon, 6 Jan 2014 11:45:43 +0000	[thread overview]
Message-ID: <52CA9767.4040101@imgtec.com> (raw)
In-Reply-To: <201401051727.10564.vapier@gentoo.org>

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
> -mike
>

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.

-- 
markos


------------------------------------------------------------------------------
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
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-01-06 11:45 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 [this message]
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=52CA9767.4040101@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.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