<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 13, 2018 at 9:18 AM, Michal Nowak <span dir="ltr"><<a href="mailto:mnowak@startmail.com" target="_blank">mnowak@startmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 09/12/18 08:42 PM, Till Wegmüller wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Aurelian<br>
<br>
Nice work.<br>
<br>
I tested a few Rust programs acros github trending at random to see how<br>
we are with workflow compliance.<br>
<br>
cargo seems to work and can be used to install programs.<br>
Tested:<br>
<a href="https://github.com/sharkdp/bat" rel="noreferrer" target="_blank">https://github.com/sharkdp/bat</a> simple cat clone: Does not work the<br>
termios library does not know about us.<br>
<br>
<a href="https://github.com/rust-lang-nursery/rustup.rs/" rel="noreferrer" target="_blank">https://github.com/rust-lang-n<wbr>ursery/rustup.rs/</a> Seems to be very<br>
unstable... They recomend that a packager pckages it. We maybe should<br>
aswell seing that many rust utilities seem to require their very<br>
specific version of rust...... Including firefox.<br>
<br>
<a href="https://github.com/uutils/coreutils" rel="noreferrer" target="_blank">https://github.com/uutils/core<wbr>utils</a> Does not seem to like that our libc<br>
has no ENOATTR....<br>
</blockquote>
<br></span>
I guess <a href="https://github.com/Stebalien/xattr/issues/18" rel="noreferrer" target="_blank">https://github.com/Stebalien/x<wbr>attr/issues/18</a> is what you see? There's workaround for this in xattr v0.2.2, but I thought is fixed by following rust's libc patches which define ENOATTR as ENODATA:<br>
<br>
* src_vendor_libc_src_unix_solar<wbr>is_mod.rs.patch<br>
* src_liblibc_src_unix_solaris_m<wbr>od.rs.patch<br>
<br>
But yes along the way there are another platform-specific problems like:<br>
<br>
error[E0432]: unresolved import `self::libc::TIOCGWINSZ`<br>
--> /export/home/newman/.cargo/reg<wbr>istry/src/github.com-1ecc6299d<wbr>b9ec823/termsize-0.1.5/src/<wbr>nix.rs:4:33<br>
|<br>
4 | use self::libc::{STDOUT_FILENO, TIOCGWINSZ, c_ushort};<br>
| ^^^^^^^^^^ no `TIOCGWINSZ` in the root<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>Thank you both for testing the package :)<br></div><div><br></div><div>We should probably get in touch with Rust developers to fix the build issue when rustc is installed and see what it would take to get some level of CI up and running.<br></div><div><br></div><div>Then we can look at Firefox 60esr...<br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
<br>
Michal</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
All in all i would say the compiler works it was saying that many<br>
packages were compiling without errors. But the work has just begun.<br>
There seems to be very much platform specific code in rust libraries in<br>
the wild.<br>
<br>
Keep up the good work<br>
Greetings<br>
Till<br>
<br>
On 09/12/18 02:30 PM, Aurélien Larcher wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For anyone interested there is a testing package of rust 1.28 at<br>
<br>
<a href="https://pkg.openindiana.org/gcc-next/" rel="noreferrer" target="_blank">https://pkg.openindiana.org/gc<wbr>c-next/</a><br>
<br>
pkg://userland/developer/lang/<wbr>rustc@1.28.0,5.11-2018.0.0.0:2<wbr>0180912T121658Z<br>
<br>
The repository is built with gcc-8 so a new BE and a good bandwidth are<br>
required.<br>
<br>
-- <br>
---<br>
Praise the Caffeine embeddings<br>
<br>
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a></div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font style="font-family:courier new,monospace" size="1">---<br>Praise the Caffeine embeddings<br></font></div></div></div></div>
</div></div>