| 1 |
On 08/17/2016 10:24 AM, siefke_listen@×××.de wrote: |
| 2 |
> On Wed, 17 Aug 2016 08:36:12 -0400 james <garftd@×××××××.net> wrote: |
| 3 |
> |
| 4 |
>> On 08/16/2016 04:43 PM, Silvio Siefke wrote: |
| 5 |
>>> Please submit a full bug report |
| 6 |
> |
| 7 |
> https://bugs.gentoo.org/show_bug.cgi?id=591514 |
| 8 |
> |
| 9 |
> Silvio |
| 10 |
> |
| 11 |
> |
| 12 |
Reading the bug, here is a request for specific info:: |
| 13 |
|
| 14 |
" Alex Xu (Hello71) 2016-08-17 15:26:17 UTC |
| 15 |
please attach example build.log" |
| 16 |
|
| 17 |
If you work with the requests on BGO, then they are much more likely |
| 18 |
to work on your bug, or at least process. If there are other similar |
| 19 |
bugs in BGO, then stay on top of them too. |
| 20 |
|
| 21 |
I've only mildly used clang, at this point, so it'll take somebody |
| 22 |
else to spot what's wrong, or who knows clang more deeply. But, now |
| 23 |
you can keep your posts short and precise in gentoo-user and reference |
| 24 |
your but like this BGO#591514. |
| 25 |
|
| 26 |
Also, if you are not copied on the postings to your bug, go ahead and |
| 27 |
add yourself directly to the "cc list". |
| 28 |
|
| 29 |
|
| 30 |
You can also use gentoo forums or an appropriate gentoo irc channel to |
| 31 |
look for CLANG/llvm types of folks, referring them to your posted bug |
| 32 |
too, so your posts there can be short and easy to read. [1] |
| 33 |
|
| 34 |
|
| 35 |
[1] |
| 36 |
https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas/Clang_native_support |
| 37 |
|
| 38 |
|
| 39 |
hth, |
| 40 |
James |
Archives