<p dir="ltr">I did it and I am rebuilding </p>
<div class="gmail_extra"><br><div class="gmail_quote">Le 6 nov. 2016 3:40 PM, "Sylvestre Ledru" <<a href="mailto:sylvestre@mozilla.com">sylvestre@mozilla.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I guess limiting the declaration of this package in the build dep should be enough<br>
<br>
S<br>
<br>
Le 06/11/2016 à 13:34, Sylvestre Ledru a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Looks lile g++-multilib is not available on many archs<br>
<br>
<a href="https://buildd.debian.org/status/package.php?p=llvm-toolchain-3.8" rel="noreferrer" target="_blank">https://buildd.debian.org/stat<wbr>us/package.php?p=llvm-toolchai<wbr>n-3.8</a><br>
<br>
could you have a look?<br>
<br>
Thanks<br>
<br>
S<br>
<br>
<br>
<br>
Le 01/11/2016 à 21:24, Sylvestre Ledru a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 01/11/2016 à 19:56, Norbert Lange a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
we absolutely should do this. I believe we have some communication<br>
problems, because I brought this up multiple times.<br>
</blockquote>
Probably me, sorry :/<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am not sure how to solve it, I can think of multiple ways. But it<br>
would help if you just apply this path as it is, and let it build for<br>
the ~10 architectures. Can you do this somehow, maybe just keep it in<br>
experimental?<br>
</blockquote>
I don't think this is reasonable leave it as it.<br>
I would like to see this changes in 3.8 and this will impact too much Debian.<br>
<br>
So, we should find a proper solution.<br>
However, I "only" saw the i386 files, not armel or others.<br>
What should be the result on arm archs?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
First, it helps if we know we start with a working build (on all<br>
platforms) before modifying it, and which libraries would normally be<br>
built.<br>
Then I would like to be able to make a list of libraries for all<br>
architectures, since I believe this will differ alot.<br>
</blockquote>
<br>
$ debdiff /tmp/libclang-common-3.8-dev_3<wbr>.8.1-12_amd64.deb libclang-common-3.8-dev_3.8.1-<wbr>13_amd64.deb<br>
[The following lists of changes regard files as different if they have<br>
different names, permissions or owners.]<br>
<br>
Files in second .deb but not in first<br>
------------------------------<wbr>-------<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/<a href="http://libclang_rt.asan-i386.so" rel="noreferrer" target="_blank">libclang_rt.asan<wbr>-i386.so</a><br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/<a href="http://libclang_rt.asan-i686.so" rel="noreferrer" target="_blank">libclang_rt.asan<wbr>-i686.so</a><br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>-preinit-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>-preinit-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>_cxx-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.asan<wbr>_cxx-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.buil<wbr>tins-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.buil<wbr>tins-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.cfi-<wbr>i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.cfi-<wbr>i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.cfi_<wbr>diag-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.cfi_<wbr>diag-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.prof<wbr>ile-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.prof<wbr>ile-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.safe<wbr>stack-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.safe<wbr>stack-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.ubsa<wbr>n_standalone-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.ubsa<wbr>n_standalone-i686.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.ubsa<wbr>n_standalone_cxx-i386.a<br>
-rw-r--r-- root/root /usr/lib/llvm-3.8/lib/clang/3.<wbr>8.1/lib/linux/libclang_rt.ubsa<wbr>n_standalone_cxx-i686.a<br>
<br>
this could be the opportunity to move them into a (or several) dedicated packages.<br>
<br>
So, we could create:<br>
libclang-sanitizer => with the libraries for the arch<br>
and<br>
libclang-sanitizer-multilib => with the libraries for the other supported archs (i386 for amd64, arm* for other I guess)<br>
<br>
I don't think we can use some voodoo-multiarch magic here :/<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also (I brought this up before): I dont know if the shared sanitizer<br>
libraries are actually used anywhere. The static libraries dont make<br>
problems, so if we can drop the shared ones then this is one problem<br>
solved.<br>
</blockquote>
You are talking about <a href="http://libclang_rt.asan-i386.so" rel="noreferrer" target="_blank">libclang_rt.asan-i386.so</a> and <a href="http://libclang_rt.asan-i686.so" rel="noreferrer" target="_blank">libclang_rt.asan-i686.so</a>, right?<br>
<br>
S<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote></div></div>