Hello, On Monday, February 26, 2024 4:38:35 PM EST Fabio Valentini wrote: > > I've run across a strange problem building a package that has some rust > > files in it. The build goes fine until the end when it starts to check for > > shebangs. It ends like this: > > > > > > /usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/s > > rc/ lib.rs has shebang which doesn't start with '/' ([no_std]) > > > > When I check the file, I find this: > > #![no_std] > > > > #[macro_use] > > mod allocated_memory; > > mod stack_allocator; > > mod allocated_stack_memory; > > > > Not being a rust programmer, I have no good idea what the code is doing. > > I can't patch this code to move it off the first line because it's > > vendored code. > > > > Is there a way to tell rpmbuild not to worry about this? > > The solution should be simple - remove stray +x permissions from all *.rs > files. Thanks. That did it. -Steve -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
