<div dir="ltr"><div class="gmail_extra">Hi Dan,</div><div class="gmail_extra"><br><div class="gmail_quote">On 13 November 2014 at 23:35, Dan McGregor <span dir="ltr"><<a href="mailto:danismostlikely@gmail.com" target="_blank">danismostlikely@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2iq" class="a3s" style="overflow:hidden">Looks like I needed to use the same security CFLAGS as gcc-runtime and<br>
libgcc. There's a new version up on my bitbucket page.<br></div></blockquote></div><br>I see you're still using anonymous python instead of COMPATIBLE_HOST to mark what architectures the sanitizers work on, can you change that?</div><div class="gmail_extra"><br></div><div class="gmail_extra">For packagegroups, if my recollection is correct and the problem is that a packagegroup wants to depend on packages which are architecture-specific, a common trick is to do something like this:</div><div class="gmail_extra"><br></div><div class="gmail_extra">SANITIZERS="gcc-sanitizer"</div><div class="gmail_extra">SANITIZSERS_mips = ""</div><div class="gmail_extra"><br></div><div class="gmail_extra">RDEPENDS_packagegroup_foo = "${SANITIZERS}"</div><div class="gmail_extra"><br></div><div class="gmail_extra">(see the tools-profile packagegroup which does this heavily)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>