aboutsummaryrefslogtreecommitdiffstats
path: root/unmaintained/ruby-rails-dom-testing4.2
diff options
context:
space:
mode:
authorGustavo Romero <gromero@br.ibm.com>2017-03-29 19:10:59 +0000
committerWilliam Pitcock <nenolod@dereferenced.org>2017-03-29 20:15:45 +0000
commit70e8624cec8394b1517a6a0dcba72bbb0c9b9e74 (patch)
treebe4ae6b582b48c608e8def2160678f0766daaec9 /unmaintained/ruby-rails-dom-testing4.2
parent995ff2aa9e9ad92979864eb3d23884eb90952793 (diff)
downloadaports-70e8624cec8394b1517a6a0dcba72bbb0c9b9e74.tar.bz2
aports-70e8624cec8394b1517a6a0dcba72bbb0c9b9e74.tar.xz
main/strace: fix pt_regs collision on ppc64le
strace build requires <linux/ptrace.h> and it includes <asm/ptrace.h> that, by its turn, defines the pt_regs struct. However the same struct is also define in <bits/user.h> from musl-dev, creating therefore a conflict. A solution is to add the __ASSEMBLY__ guard so pt_regs struct from <asm/ptrace.h> is not include twice, avoiding the collision in question. There is no other way to worki around that issue on Musl since it does not include the linux headers and hence has to define again the pt_regs struct in user.h and the name clashes. In glibc, for instance, user.h includes <asm/ptrace.h> from kernel and does not redefine it. Also Musl community has no better solution at the moment for this issue on ppc, so basically nothing change since [1]. [1] http://www.openwall.com/lists/musl/2016/12/30/5
Diffstat (limited to 'unmaintained/ruby-rails-dom-testing4.2')
0 files changed, 0 insertions, 0 deletions