Rust June 2017

rust@lists.fedoraproject.org

6 participants
4 discussions

Re: [opensuse-packaging] Packing Rust Applications
by Neal Gompa 18 Jun '17

18 Jun '17

On Sun, Jun 18, 2017 at 10:27 AM, Michael Aquilina <michaelaquilina(a)gmail.com> wrote: > Thanks for this. Is there anywhere apart from the issue and PR you > linked to that I could follow progress on this? > The Rust SIG holds meetings somewhat regularly (when there's something to talk about) on Wednesdays each week. The logs are posted here: https://docs.pagure.org/fedora-rust.sig/ The Rust SIG content is all hosted at Pagure: https://pagure.io/group/fedora-rust Also feel free to join the Fedora Rust SIG mailing list: https://lists.fedoraproject.org/admin/lists/rust.lists.fedoraproject.org/ (rust(a)lists.fedoraproject.org) -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

Re: [opensuse-packaging] Packing Rust Applications
by Neal Gompa 18 Jun '17

18 Jun '17

On Sun, Jun 18, 2017 at 9:03 AM, Michael Aquilina <michaelaquilina(a)gmail.com> wrote: > I'm trying to package ripgrep within OBS but it seems like github is > unreachable by the OBS virtual machines (presumably because it's a > security issue?). > > Cargo needs to contact github to retrieve the necessary crates and > compile the binary. > > [ 13s] + cargo build --release --verbose > [ 13s] Updating registry `https://github.com/rust-lang/crates.io-index` > [ 13s] warning: spurious network error (2 tries remaining): [12/-1] > curl error: Could not resolve host: github.com > [ 13s] > [ 13s] warning: spurious network error (1 tries remaining): [12/-1] > curl error: Could not resolve host: github.com > [ 13s] > [ 13s] error: failed to fetch `https://github.com/rust-lang/crates.io-index` > [ 13s] > [ 13s] Caused by: > [ 13s] [12/-1] curl error: Could not resolve host: github.com > [ 13s] > > What is the recommended way of packaging rust applications if there is > no access to the crate index? > > It's probably worth mentioning that this builds successfully with rpmbuild > Luke Jones has been working on bringing in the necessary packaging capabilities (including macros) for Rust to openSUSE. Along with myself, Igor Gnatenko, Josh Stone, and Rémi Verschelde, we've been working on creating a standard packaging practice for Fedora, Mageia, and openSUSE for Rust. At this time, I believe it's not quite possible yet outside of the Rust playground for Fedora on COPR[1], as we depend on new functionality for RPM that is in development[2][3]. I'm working with Luke on porting the respective changes to openSUSE so that we can have a similar playground on OBS for Rust things. [1]: https://copr.fedorainfracloud.org/coprs/g/rust/playground/ [2]: https://github.com/rpm-software-management/rpm/issues/159 [3]: https://github.com/rpm-software-management/rpm/pull/164 -- 真実はいつも一つ！/ Always, there's only one truth!

2 3

[HEADS UP] crates are now built in COPR
by Igor Gnatenko 15 Jun '17

15 Jun '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hey there, some of you might know that since yesterday's morning COPR supports turning on (thanks to clime) new feature implemented in mock (thanks to mich181189) -- use_bootstrap_chroot. It took me only few days to update crates in playground repository to latest shiny versions (only 75 commits) and now we have (almost) all packages built in COPR repo[0]. So, feel free to remove rust-sig repo and replace it with COPR one: # rm -f /etc/yum.repos.d/rust-sig.repo # dnf -y copr enable @rust/playground P.S. so far we have only 3 utilities there -- ripgrep, rustfilt, rustfmt [0] https://copr.fedorainfracloud.org/coprs/g/rust/playground/ - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAllC7o8ACgkQaVcUvRu8 X0xhMA/9ESN3w3crd1LN84C0Z6zngF3C+fRa/CIAConIoeE79KaLWTV3oteorkA6 wMg+S4rEd1xuwqP9hHeAPj7LYKZW947xvM+IJLuaIeeFPOzua8rdZEbUhORChCE6 CM4N3DzbRRIx5OKvR9HQhzR6BPJS3UvF6z4NTownq8MHiUP20WL9hhelQ1fhnVXB oIWNK8EfQGuFCgJbkiqvSsbpu1msYxb+Rkq37qANur8jatQsYVXtixkv2H6T7V2r GfmkxlOPIBy7LULY+S5znNJEPMCF6AhWJ+CbvYkIVcLein3bD8iDevDC3rIrIYhk FgIte5hyi6xat9bdLG2mpqM80DvtoxwM3+atuXLDB/ZEYkPSefHWFCySvfDJWJat +EPJWmnzi7xMDuiU1zQD129dyox5MDDHJWnBLxsbtyR3CvibG2EG3EG3FSt5ApLJ D/qy/y5rwzRmQ3oYvVHHFGse8JPqApehT8hsfoRYzKaWwCtexkO5Cez/CnZ/U3rd otfUkzxdU34VxdvFI4CbnM9H21Hb5B2QUNPQoRzXSalJihu4CCatbcvuTQsoCRVj HkE0+bSf3FrxRNeYmnLVzB9XYGNMCnAENaoPNRWLVfUJ7pz4UgW8pg6vacGoWGKM awgZqZiIudppHzkNKspFA4BSasu1H3TN8Ouo1aydx7vxYNlXSOc= =sQ2j -----END PGP SIGNATURE-----

1 0

Build failures on Debian
by Ximin Luo 06 Jun '17

06 Jun '17

Hi Fedora rust list, I'm getting build errors for rust 1.17.0 in armhf and ppc64el in Debian: https://github.com/rust-lang/rust/issues/42476 ppc64el LLVM ERROR: Undefined temporary symbol https://github.com/rust-lang/rust/issues/42477 armhf SIGILL I see OTOH that your builds succeeded on these platforms: https://koji.fedoraproject.org/koji/packageinfo?packageID=rust Your LLVM 3.9 has a lot of patches: https://src.fedoraproject.org/cgit/rpms/llvm3.9.git/tree/ Ours also: https://sources.debian.net/src/llvm-toolchain-3.9/1:3.9.1-9/debian/patches/ Diff between ours and rust's LLVM: https://gist.github.com/infinity0/873566481db105fea47630da88e1b632 In particular, rust-lang-llvm-pr67.patch (0032-Fix-computeKnownBits-for-ARMISD-CMOV.patch) seems to fix some correctness issues on ARM but I'm not sure if this is responsible for the SIGILL that we're seeing, what do you think? Then, I have no idea about the ppc64el error, but I was wondering if you've seen it before. We didn't see it for 1.16 or earlier versions. I had removed the ppc64el workaround for https://github.com/rust-lang/rust/issues/37320 for 1.17.0 but this was a segfault and not an "Undefined temporary symbol". And the error also happens when cross-compiling from x86-64 to ppc64el, so I'm led to believe it's something to do with the codegen algorithm rather than any architecture-specific code that is run. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

2 1

2024

2023

2022

2021

2020

2019

2018

2017

Rust June 2017