QA Notices in 0.8 #2
Assignees
Comments
ghost
assigned 
|
Yes, I'm getting the same, will try to handle it / check if it possible |
|
Also note that I remove some stuff from it just after install rm -f "${ED}/usr/$(get_libdir)/librusti.so" || die
rm -f "${ED}/usr/$(get_libdir)/librustc.so" || die
rm -f "${ED}/usr/$(get_libdir)/librust.so" || die
rm -f "${ED}/usr/$(get_libdir)/librustpkg.so" || die
rm -f "${ED}/usr/$(get_libdir)/librustdoc.so" || die |
|
Is it gone now? |
|
Probably RPATHs will be gone (see rust-lang/rust#11747), but RUNPATHs and SONAMEs problems remains for now. (I don't know any issue about them) |
|
Ah, I confirmed that notice about RUNPATHs disappears now. I'm sorry. The remaining messages are: |
|
Sorry, I was out of town for a bit and unable to test this. Using .10 now, still get the warnings I mentioned above. I used dev-lang/rust::rust as the atom, so I'm pretty sure I'm pulling from the overlay, not the base tree. Also, this, but as it says, I don't think it's on you guys, but on upstream. |
|
@gotyaoi The libuv problem had been fixed on both upstream and Rust 0.11.0 (and master, of course). Some other problems may also fixed on the 0.11.0 release. |
|
@gotyaoi @omasanori someone has added ebuild to tree : http://gpo.zugaina.org/dev-lang/rust but there is no 0.11 yet |
|
@Heather Oh, I didn't noticed that. |
|
@omasanori maybe it also will be reasonable to ping https://github.com/jauhien At least because we should have 0.11 in tree and he is official maintainer now so it will be a bit wrong for me to bump it there ;) |
|
0.11.0 version bump has been requested. |
|
@omasanori: yes, let's discuss it. In a moment I'll push 9999 version, so the current issues will be solved and we can discuss next steps toghether. |
|
Sorry for delay, i was busy ( |
|
See issue #24 |
|
Is there something do to here anymore? |
|
yes but it was closed afair |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Got a bunch of QA notices that i don't remember from 0.6 or 0.7...
The text was updated successfully, but these errors were encountered: